Cortex MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CORTEX_DATA_DIR | No | Absolute directory path to override the default local data directory for Cortex MCP storage. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cortex_healthB | Check that the Cortex MCP server is responding. |
| cortex_create_claimC | Register a claim and its verification criteria in a project. |
| cortex_add_evidenceC | Record evidence and its claimed provenance for an existing claim. |
| cortex_track_assumptionC | Register an unverified assumption with optional caller-reported confidence. |
| cortex_update_assumptionC | Record a caller-reported assumption status and its reason. |
| cortex_reviewA | Review a claim or get an advisory decision recommendation under the project policy. A decision needs at least one claim or assumption reference. |
| cortex_get_contextC | Recover recent records for selected collections in one project. Review results are summaries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool maps to a distinct action and object: creating claims, adding evidence, tracking or updating assumptions, reviewing, retrieving context, and checking health. The boundaries between review and context retrieval, and between creating and updating assumptions, are clear from the descriptions.
All tools use the same cortex_ prefix and snake_case conventions, with mostly verb_noun names such as create_claim, add_evidence, and get_context. Minor deviations are cortex_health, a noun, and cortex_review, a bare verb.
Seven tools is well-scoped for a claim/evidence/assumption review server. Each tool has a clear role without obvious redundancy.
The surface covers the core workflow of creating claims, attaching evidence, tracking assumptions, reviewing, and retrieving context. Minor gaps exist around updating or deleting claims and evidence, but the append-only audit-style design may make some of these unnecessary.