Built for scale
Manage a fleet of MCP servers without third-party gateways or bespoke routing layers.
docs.mcp-runtime.org
Launch MCP servers with a platform, not a patchwork.
MCP Runtime Platform gives teams a registry, Kubernetes operator, and CLI that standardizes how MCP servers are defined, built, and routed.
At a glance
Everything you need to ship MCP servers confidently.
- Metadata-driven server definitions in YAML.
- Operator creates Deployment, Service, and Ingress automatically.
- Internal registry keeps images and metadata in sync.
- Unified routes for every server at /{server-name}/mcp.
1 CLI
Unified workflow for platform and servers.
3 core services
Registry, operator, and cluster helpers.
0 bespoke YAML
No hand-written manifests for each server.
Why MCP Runtime Platform
Move from experiments to production with a clear, repeatable approach to deploying and cataloging MCP servers.
Designed for teams
A centralized registry and consistent deployment flow make it easy to discover and reuse servers.
Opinionated safety
Promote best practices with standardized metadata and CI-ready pipelines.
Platform features
Ship repeatable deployments with tooling built for MCP server fleets.
Complete platform
Deploy registry, operator, and helpers in one setup flow built for MCP fleets.
CLI tooling
Manage platform setup, registry operations, and server pipelines from one CLI.
Kubernetes operator
Creates Deployment, Service, and Ingress resources from MCP metadata.
Metadata-driven
Define MCP servers in YAML without hand-writing Kubernetes manifests.
Unified routing
Every MCP server is reachable at a consistent /{server-name}/mcp path.
Automated builds
Build Docker images from metadata and keep registry entries up to date.
End-to-end workflow
Standardize how teams go from definition to routed MCP servers.
01
Define
Capture server metadata in YAML, including name, route, and container port.
02
Build
Build Docker images locally or in CI/CD and push them to the registry.
03
Deploy
Generate manifests and deploy MCP servers through the operator.
04
Access
Reach every MCP server through consistent URLs managed by ingress.
Platform architecture
Designed to fit right into your existing delivery pipeline.
Developer workstation
Define servers, build images, and push updates from local development.
CI/CD pipeline
Build images, publish to the registry, and generate CRDs automatically.
Kubernetes cluster
The operator watches MCPServer resources and provisions services.
Internal registry
Stores MCP server images and keeps metadata in sync for discovery.
Active development notice
MCP Runtime Platform is under active development. APIs, commands, and behavior may change, and production usage is not recommended yet.