We're building the operational layer for MCP.
MCPG is a small team obsessed with one thing: making MCP traffic safe, observable, and operable at production scale. We chose Rust for the runtime, Apache-2.0 for the core, and an open RFC process for the design.
What we believe
- Protocol layer of agent infrastructure should be open. The gateway, the SDK, the CLIs, and the free plugins are Apache-2.0; the enterprise plugins and fleet platform are source-available under BUSL-1.1 and auto-convert to Apache-2.0 three years after each release. Everything we publish can be read, audited, and patched.
- Single binary beats microservices for ops layers. When everything else is on fire, the operational layer must work. One Rust binary is easier to reason about than ten Kubernetes deployments.
- Depth over breadth. AWS will out-distribute us. We win by being the deepest MCP protocol engineering shop in the market. We maintain a public conformance suite and we score against it.
- Dogfood-driven. mcpg.dev itself runs through MCPG. Our own control plane is an MCP workspace. If it breaks for us, it breaks for customers — that's a forcing function we don't want to lose.
Where we are
Public beta. The gateway runtime, 93+ signed plugins, the control plane, the Kubernetes operator, and the Helm chart are running in production at design-partner orgs. The managed cloud is in public beta. We're targeting 1.0.0 GA in 2026.
The team
A small group of engineers who've shipped policy engines, gRPC streaming protocols, plugin runtimes, and observability pipelines. We're hiring — see the contact page.
Working with us
Design partners get migration support, dedicated Slack, and direct input on the 1.0 roadmap. If you're running MCP at any non-trivial scale, we want to talk.