We built LLM gateway with this goal to provide a single place to manage authentication, authorization, routing, and observability for MCP servers, with a path toward a more general agent-gateway architecture in the future.
The system includes a central MCP registry, support for OAuth2/DCR integration, Virtual MCP Servers for curated toolsets, and a playground for experimenting with tool calls.
Resources -
Architecture Blog – Covers the N×M problem, gateway motivation, design choices, auth layers, Virtual MCP Servers, and the overall model.
https://www.truefoundry.com/blog/introducing-truefoundry-mcp...
Tutorial – Step-by-step guide to writing an MCP server, adding Okta-based OAuth, and integrating it with the Gateway.
https://docs.truefoundry.com/docs/ai-gateway/mcp-server-oaut...
Feedback on gaps and edge cases is welcome.
deeptishukla22•1h ago
- M2M-issued short-lived tokens for backend → MCP calls
- Per-request user metadata injection so tool calls can still act on behalf of the user
- Consistent OAuth2 / Okta validation so both layers trust each other
Was looking for this standarization.