Research preview · early access list open

The self-hosted MCP gateway your security team won't block.

Multiuser OAuth, tool-level quarantine, and audit log export. Runs as a single Go binary in your own Kubernetes cluster. No SaaS vendor in your agents' data path.

From $799/mo for teams up to 25 engineers (planned pricing). Free OSS personal edition — always. View on GitHub

The MCP governance gap is a 2026 problem, not a 2027 problem.

1

Every AI agent in your org now reaches internal APIs. You can’t audit what they call.

2

You can’t revoke access to one misbehaving tool without nuking the whole LLM integration.

3

Your cloud vendor is not going to solve this — and if they do, your MCP data leaves your cluster.

What we're building

The underlying code exists in the open-source MCPProxy repo under a server build tag and is being hardened for production use. Everything below is built. The commercial tier is a polish and packaging exercise.

Multiuser OAuth

Google, GitHub, or Microsoft identity. Per-user workspace isolation. JWT bearer tokens for MCP clients. Tokens stay in your cluster.

Tool-level quarantine

SHA-256 hash-based change detection. New tools stay quarantined until approved. Rug-pull protection for mutating tool descriptions.

Audit log export

Every tool call logged with request ID, user, and intent. JSONL export for SIEM pipelines. Request-ID correlation across proxy and upstream.

Prometheus metrics

Request rates, error rates, tool-call latency per upstream server. Drop-in for your existing Grafana dashboards. No vendor telemetry.

Why self-hosted

If your MCP data can't transit a vendor's control plane, most gateways are out.

Capability MCPProxyObotOkta Agent GatewayKong AI GatewayHeliconeLangfuse
Self-hosted Cloud first Enterprise only
Single binary
Open-source core Core OSS
Data stays in your cluster Partial Partial
Annual price (team tier) $799/mo (planned) Contact sales Contact sales $100/mo/model $799/mo $199/mo

Competitor pricing verified 2026-04-15 from public pricing pages. Subject to change.

Planned pricing

your input will shape this

These tiers are not available yet. We're gauging interest and gathering feedback before finalizing.

Personal

Free

Open source, forever

  • Unlimited personal use
  • BM25 tool discovery
  • Docker isolation
  • Tool quarantine
  • Desktop tray app
Planned

Team

$799/mo

Annual billing · up to 25 seats

  • Multiuser OAuth (Google/GitHub/Microsoft)
  • Per-user workspace isolation
  • Tool-level quarantine
  • Prometheus metrics export
  • Audit log export
  • 48h email support SLA

Same price as Helicone Team. Runs in your own cluster. Your data never leaves.

Planned

Enterprise

Contact

From $2,499/mo · unlimited seats

  • Everything in Team
  • SSO / SAML
  • SLA
  • Deployment assistance
  • Private Slack channel

Help us build this right.

We're talking to platform engineering teams who are hitting MCP governance problems today. If you're one of them, tell us what you need. No sales call. Just a 4-question survey, and we'll share what we learn.

Questions

Is this available today? +

The open-source MCPProxy is — install it from GitHub now. The commercial Team tier is in development. We’re gauging interest and gathering feedback to decide whether and when to ship it.

How’s it different from Obot, Kong AI Gateway, or Okta Agent Gateway? +

All three are excellent for their target buyer. MCPProxy Team is specifically for teams that need the multiuser OAuth and audit story but cannot put their MCP data in a vendor-managed control plane: regulated industries, air-gapped environments, multi-cloud or on-prem Kubernetes.

When will it be available? +

That depends on what we hear from you. If there’s clear demand, we’ll prioritize it. If not, we’ll keep focus on the open-source project and revisit later.

Will I get priority access? +

Yes. Everyone on this list hears first when we have something to show, before we announce publicly.

What about OAuth token passthrough to upstream MCP servers? +

Single sign-on at the proxy that federates to upstream MCP servers is a feature we’re actively exploring, pending the MCP spec standardizing token exchange. If you need this today, tell us in the survey — it helps us prioritize.