Self-hosted federated MCP gateway: one OAuth 2.1 MCP server in front of N apps, user-level scopes.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like cortex-gateway.
https://mcp.cortex-gateway.dev/mcp{
"CORTEX_CANONICAL_URI": "YOUR_VALUE_HERE",
"OAUTH_ISSUER": "YOUR_VALUE_HERE",
"CORTEX_BACKENDS": "YOUR_VALUE_HERE",
"CORTEX_TECHNICAL_TOKEN": "YOUR_SECRET_VALUE"
}Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-wellknownmcp-cortex-gateway": {
"url": "https://mcp.cortex-gateway.dev/mcp"
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
cortex-gateway is an MCP server for Self-hosted federated MCP gateway: one OAuth 2.1 MCP server in front of N apps, user-level scopes.. It supports HTTP transport.
Use the generated config in Install. It points your client at the advertised remote endpoint shown on this page.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://mcp.cortex-gateway.dev/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://mcp.cortex-gateway.dev/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://mcp.cortex-gateway.dev/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://mcp.cortex-gateway.dev/mcp.
cortex-gateway uses HTTP transport. Endpoint: https://mcp.cortex-gateway.dev/mcp.
cortex-gateway inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
cortex-gateway is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
ghcr.io/wellknownmcp/cortex-gateway:v0.2.0streamable-http | oci | Not captured | Env: CORTEX_CANONICAL_URI required Env: OAUTH_ISSUER required Env: CORTEX_BACKENDS required Env: CORTEX_TECHNICAL_TOKEN required secret |