We have GitHub Enterprise Server and would like to expose the MCP to be accessible as a central service so the MCP clients can access them.
Running it in stdio mode restricts a lot of possibilities we could have today.
Why this feature is important:
-
Centralized Access & Scalability:
Running MCP as a standalone server allows multiple clients to access the service concurrently, enabling centralized management and reducing duplication of MCP instances across an organization.
-
Improved Integration:
A server-based approach makes it easier to integrate MCP with other enterprise tools and services that rely on a persistent, network-accessible endpoint—something not possible with stdio mode.
-
Enhanced Monitoring & Observability:
Standalone mode enables integration with logging, monitoring, and alerting systems, providing better visibility into the health and usage of the MCP service.
-
Security & Access Control:
Exposing MCP as a network service allows for standardized authentication, authorization, and auditing, which are essential for enterprise environments.
-
Reliability & Fault Tolerance:
Running as a service enables use of failover mechanisms and load balancing, improving the overall reliability and uptime of MCP for all clients.
-
Future-proofing:
As organizations grow, the need for scalable and maintainable infrastructure becomes critical. Supporting a standalone mode ensures MCP can meet evolving enterprise requirements.
We have GitHub Enterprise Server and would like to expose the MCP to be accessible as a central service so the MCP clients can access them.
Running it in stdio mode restricts a lot of possibilities we could have today.
Why this feature is important:
Centralized Access & Scalability:
Running MCP as a standalone server allows multiple clients to access the service concurrently, enabling centralized management and reducing duplication of MCP instances across an organization.
Improved Integration:
A server-based approach makes it easier to integrate MCP with other enterprise tools and services that rely on a persistent, network-accessible endpoint—something not possible with stdio mode.
Enhanced Monitoring & Observability:
Standalone mode enables integration with logging, monitoring, and alerting systems, providing better visibility into the health and usage of the MCP service.
Security & Access Control:
Exposing MCP as a network service allows for standardized authentication, authorization, and auditing, which are essential for enterprise environments.
Reliability & Fault Tolerance:
Running as a service enables use of failover mechanisms and load balancing, improving the overall reliability and uptime of MCP for all clients.
Future-proofing:
As organizations grow, the need for scalable and maintainable infrastructure becomes critical. Supporting a standalone mode ensures MCP can meet evolving enterprise requirements.