Auto-Managed Lifecycle
Servers start automatically when needed and stop after idle periods. No manual process management. Configure once, run forever.
Hot Reload Configuration
Update your server catalog without restarting the gateway. Changes are detected automatically and applied in milliseconds.
Multiple Runtime Backends
Local processes, remote HTTP/SSE, Docker containers, and Kubernetes. One gateway, any deployment model.
Dual Transport Support
HTTP/REST API for web applications. Stdio wrapper for Claude Desktop and Cline. Same servers, any client.
Rust-Native Performance
Memory-safe, zero-cost abstractions, and async I/O. Minimal footprint with maximum throughput.
Vendor Neutral
Not locked to Docker or any platform. Works with your existing infrastructure. Open source under Apache-2.0.
Simple YAML Configuration
Define all your MCP servers in a single catalog file. The gateway handles the rest.
servers:
- id: postgres
display_name: PostgreSQL Tools
runtime:
type: local-process
command: postgres-mcp
env:
DATABASE_URL: ${DATABASE_URL}
- id: github
display_name: GitHub API
runtime:
type: remote-sse
url: https://mcp.github.example.comRESTful API
Full HTTP API for server management and MCP communication. Works with any HTTP client.
# List servers
GET /servers
# Start a server
POST /servers/postgres/start
# Send MCP request
POST /mcp
{
"server_id": "postgres",
"method": "tools/list"
}
# Hot reload catalog
POST /admin/reloadBuilt For Your Use Case
Development Teams
Share MCP server configurations across your team via Git. Everyone uses the same servers with consistent settings.
Production APIs
Deploy the gateway as your MCP backend. Auto-lifecycle management reduces compute costs by 80%.
Desktop Users
Centralize your Claude Desktop MCP config. Update servers without editing JSON files or restarting.
Ready to Simplify Your MCP Infrastructure?
Get started in under 5 minutes. No complex setup required.