{"repo":"wellknownmcp/cortex-gateway","free":true,"listed":false,"github":"https://github.com/wellknownmcp/cortex-gateway","clone":"git clone https://github.com/wellknownmcp/cortex-gateway.git","description":"Federated MCP gateway: one OAuth 2.1-protected, spec-compliant MCP server in front of all your apps. Backends stay plain HTTP (~120-line contract) or proxied native MCP servers with a per-user token vault. Scope-filtered tools, live discovery, audit trail. Give agents curated, governed access to your whole stack — one URL, one token.","language":"HTML","stars":10,"topics":["ai-agents","federation","gateway","mcp","model-context-protocol","oauth2"],"license":"MIT","category":"mcp-servers","readme_excerpt":"Cortex Gateway A federated MCP gateway: one spec-compliant, OAuth-protected MCP server in front of N plain-HTTP backends. Your business apps stay ordinary web services. Each one exposes a single POST /api/cortex/backend endpoint (a 120-line contract, no MCP library, no stdio). The gateway discovers their tools, merges them into one MCP catalog, enforces OAuth 2.1 + scopes, routes tools/call to the owning backend, and keeps a pseudonymized audit trail. Built for one requirement: everyone in a company should be able to hand their own agent the keys — with exactly that person's rights, nothing more, nothing less. And when agents become autonomous assistants, the answer stays the same: the agent borrows the person's identity, the apps keep enforcing that person's rights. The gateway decides nothing, so there is nothing new to trust. Put another way: zero-trust principles for AI agents — the missing link between your IAM (who your users are, what they may do) and the MCP ecosystem (how agents call tools). Not a full ZTNA product; the identity-and-access layer for agents. A backend is a dedicated MCP reduced to its essence: a tool catalog plus tool invocation (and optional prompts/resources) over bare HTTP JSON-RPC — the transport and lifecycle machinery (initialize, sessions, SSE, version negotiation) lives once, in the gateway. Because the contract is a semantic subset of MCP, a native MCP server can also be federated through the built-in MCP→backend proxy adapter (docs/mcp-adapt","default_branch":null,"files":null,"tree":[],"storefront":"/r/wellknownmcp","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/wellknownmcp/cortex-gateway/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}