Gateway
The OAuth layer you keep meaning to build.
PKCE, dynamic client registration, redirect policies, refresh, encrypted grant storage. None of this is why your users pay you. We’ve already built it. You attach it to whatever MCP server you already have — ours, FastMCP, or your own.
Claude, ChatGPT, Cursor
Gets an MCP token only
Emcy Gateway edge
Handles discovery, PKCE, and token exchange
Your API
Sees the real signed-in user
“Emcy turned our OpenAPI spec into a production MCP server in under ten minutes. The OAuth layer just worked.”
Engineering Lead
Series B SaaS
“We went from hosting our own MCP server to Emcy and cut our agent infrastructure cost by 60%.”
CTO
Developer Tools Startup
“The embedded agent SDK let us ship AI features without building a separate integration layer.”
Product Engineer
Enterprise Platform
Auth, done
OAuth is not your product. Stop spending sprints on it.
A week of reading specs, a month of fixing edge cases, then another month supporting it across every MCP client. Or: attach Gateway and move on. Same auth story, every client, no spec docs on your desk.
- Skip the week of reading and the month of fixing.
- Customer access tokens never touch the browser, ever.
- When the next MCP client launches, your auth flow already supports it.
Claude, ChatGPT, Cursor
Gets an MCP token only
Emcy Gateway edge
Handles discovery, PKCE, and token exchange
Your API
Sees the real signed-in user
Keep your runtime
Keep the server you already have. Just put a real front door on it.
You don’t have to migrate, rewrite, or move anything. If your MCP server runs somewhere — your laptop, a Fly box, FastMCP, our Host — Gateway becomes its public face.
- Don’t move infra you don’t want to move.
- Same auth flow no matter what’s behind it.
- Swap the runtime later without changing the URL your users connect to.
Tool calls (24h)
2,188
+12% vs yesterday
Avg latency
142ms
p99: 380ms
Error rate
1.3%
29 failed of 2,188
Recent tool calls
“Gateway is the production auth edge: one public URL, one auth story, one place for grants and request logs.”
Emcy platform principle
Related reads
Docs and architecture guides
Add OAuth to your MCP server
GuideConfigure the Gateway auth edge for user-scoped data and compliant client flows.
MCP OAuth in embedded mode
GuideSee how Gateway and Embed share the same-user path inside your product.
Connect a self-hosted runtime
GuideKeep your own MCP runtime and let Gateway own the public OAuth and MCP edge.
Get started
Put a real front door on your MCP server.
Add Gateway the day your users need to sign in — whether the runtime lives on Emcy Host or your own infrastructure. Embed and external clients share the same edge.