Repository navigation
Home
vMCP lets you register HTTP MCP servers and expose selected tools, resources and prompts through virtual servers. Agents connect to one endpoint with their own credentials; upstream credentials remain in the gateway.
New to vMCP? Follow Getting started for a local demo from installation to authenticated discovery. Already have a running instance? Use Guided setup to register upstreams and connect clients. Choose Installation options for Docker, Kubernetes or published releases.
vMCP is Beta / development. The supported MCP revision is 2025-06-18. Review known limitations and the production guide before production use.
- Getting started
- Guided setup and client connections
- Installation options
- Kubernetes quickstart
- Install a published release
- Upstreams
- Virtual servers
- Resources and prompts
- Agent keys and authentication
- OAuth for agents
- SSO and roles
- Tool policies
- PII masking
- Rate limits
- Audit log
- FAQ and troubleshooting
- Production deployment
- Security
- Network security
- Upstream TLS
- Upstream OAuth
- Resilience and high availability
- Observability
- Audit operations
- Audit exporters
- Security operations
- Dedicated tenant operations
- Architecture
- Configuration
- REST API and GitOps
- MCP protocol compatibility
- SSE delivery and replay
- Negotiated client features
- Authorization consistency
- Audit durability
For source builds, tests, CI and publishing, see the repository's Contributing guide and maintainer documentation. The API contract is OpenAPI.
vMCP is licensed under Apache-2.0. This wiki is generated from the docs/ folder of the repository: send documentation fixes as pull requests, not wiki edits.
- Getting started
- Guided setup and client connections
- Installation options
- Kubernetes quickstart
- Install a published release
- Upstreams
- Virtual servers
- Resources and prompts
- Agent keys and authentication
- OAuth for agents
- SSO and roles
- Tool policies
- PII masking
- Rate limits
- Audit log
- FAQ and troubleshooting