Cortex Gateway

Install

Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install connector/wellknownmcp-cortex-gateway

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 26, 2026.

Tools

5 read · 0 write · 0 delete · 1 not yet classified

Secrets

None asked for

Install scripts

None found

Runs as

Docker image

Tools (6)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• find_tools

  Returns the full schema (detailed description + inputSchema) of one or more federated tools. Only useful in `search` mode (header X-Cortex-Tool-Mode: search), where tools/list returns names and 1-line descriptions only to save LLM context. Two usages: - `names: [...]`: fetch the exact schemas of these tools (most efficient when you know what you want). - `query: "..."`: fuzzy search by name/description (case-insensitive substring). Limited to 10 results. When both are provided, `names` wins.

• list_cortex_resources

  Lists the MCP resources exposed by the gateway (self-describing architecture document, dynamic backend resources through URI templates). Wrapper tool over the resources/list channel, needed because some MCP clients do not surface the resources primitive in their visible tool palette.

• list_cortex_tickets

  Lists your own previously filed `report_missing_capability` tickets (auto-filtered by OAuth identity — you do not see other agents' tickets). Useful before re-filing a ticket, or to follow a ticket's status after triage by the platform team. Possible statuses: open (just filed), triaged (the team looked at it), planned (work scheduled), resolved (capability shipped, resolvedPrUrl points at the PR), wont_fix (deliberately not implemented, triageNote explains why), duplicate (merged with another). Returns: { tickets: [{ id, status, severity, contextTool, contextApp, whatIWanted, suggestedShape…

• read_cortex_resource

  Reads an MCP resource by URI (e.g. cortex://architecture, docs://document/42). Wrapper tool over the resources/read channel. Returns Markdown or JSON depending on the resource. Use after list_cortex_resources to discover available URIs.

• report_missing_capability

  Reports a missing capability or an insufficient tool to the platform team. Use it when you cannot fulfil a user request because no MCP tool offers what is needed, OR when an existing tool limits you (incomplete return, missing parameter, unhelpful error, ...). Typical example: the user asks for a link to a file; you search the returns of list_files / read_file, there is no webUrl field; you report the missing capability. The platform team prioritizes and ships the field in a next release. Principle: your ticket is a SIGNAL, not an implementation order. Several converging tickets = a priority…

• whoami

  Returns the caller's OAuth identity (email, sub, pool, scopes, client, audience, jti) and aggregates the whoami of every healthy federated backend (effective role in that backend, derived capabilities). Useful to know who you are and what you may do before invoking a write tool.

Signals

Stars

12

Forks

0

Open issues

2

Last commit

Aug 22, 2026 (2 months ago)

Last release

Jul 20, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.wellknownmcp/cortex-gateway

Version

0.2.0

Auth

Auth not stated, API key

Packages

oci ghcr.io/wellknownmcp/cortex-gateway:v0.2.0

License

MIT

Repository

github.com/wellknownmcp/cortex-gateway

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql