Developer · Remote MCP server
Cortex Gateway
Self-hosted federated MCP gateway: one OAuth 2.1 MCP server in front of N apps, user-level scopes.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.wellknownmcp/cortex-gateway- Version
- 0.2.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Package
- OCI image (Docker)
- Published
- 2026-07-20
- Updated
- 2026-07-20
- Publisher
- wellknownmcp (GitHub) · 5 servers with pages here
- Repository
- github.com/wellknownmcp/cortex-gateway
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.cortex-gateway.dev/mcp | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/wellknownmcp/cortex-gateway:v0.2.0 | — | HTTP |
How to connect Cortex Gateway
Cortex Gateway is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.cortex-gateway.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/wellknownmcp/cortex-gateway:v0.2.0. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL. It reads these environment variables: CORTEX_CANONICAL_URI (required), OAUTH_ISSUER (required), CORTEX_BACKENDS (required) and CORTEX_TECHNICAL_TOKEN (required, secret); set them in the client's configuration for this server.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from wellknownmcp (GitHub)
| Server | Runs |
|---|---|
| AgentHillA daily game played by AI agents: ten places on a hill, resolved every night. OAuth 2.1. | Remote · HTTP |
| Animam Agent PlatformConfigure & analyze AI chatbots: personas, corpus, tools, digests, multi-bot. OAuth 2.1. | Remote · HTTP, SSE |
| Hoshin Kanri X-MatrixStrategic memory agents can build, score and keep current: a living X-Matrix with review cadences. | Remote & Local · HTTP, stdio |
| IA-Asso.fr — French Associations RegistrySearch 1.26M+ active French associations (official RNA registry, 10 tools, premium & RUP filters) | Remote · HTTP |
More developer servers
| Server | Runs |
|---|---|
| corralctlSearch code and symbols across every clone in your corralctl workspace. Zero network calls. | Local · stdio |
| Correctover MCPCompatibility MCP server package that forwards to the correctover-mcp-gateway runtime. | Local · stdio |
| CortexLocal repo context for coding assistants with semantic search and graph relationships. | Local · stdio |
| CortexSyslog receiver and MCP server for homelab log intelligence. | Remote & Local · HTTP, stdio |
| Cortex RMCPSelf-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS. | Local · stdio |
| Cortex RMCPRust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation. | Local · stdio |
| Corvi CareersSearch remote and onsite jobs through the public Corvi Careers MCP server. | Remote · HTTP |
| Cosmic Correlation EngineAI Agent Astrology — natal charts, transits, cosmic weather, and forecasts for AI agents. | Local · stdio |