Cortex MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_knowledgeA | Search 735 knowledge fragments across 26 domains for validated patterns, skill procedures, and implementation examples. Use before writing code, designing architecture, or reviewing work to ground your approach in battle-tested practices. |
| get_fragmentA | Retrieve the full content of a specific knowledge fragment by ID (e.g. SKL-0001, PAT-0042). Use after search_knowledge returns relevant results and you need the complete procedure, pattern, or example. |
| browse_libraryA | List all available knowledge fragments, optionally filtered by category (skills, patterns, agents, examples) or domain pillar (e.g. game-dev, ecommerce). Use to discover what knowledge exists before searching. |
| detect_projectA | Analyze a list of project root filenames to detect the tech stack and suggest relevant knowledge searches. Use at project start to auto-scope knowledge to the right domains. |
| list_categoriesA | Show all categories and domain pillars with fragment counts. Use to understand library coverage and available filtering options. |
| search_metricsA | View diagnostic search metrics: query counts, tier resolution rates, zero-result frequency, and top-10 most retrieved fragments. Use to understand search quality and inform optimization decisions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| find | |
| explain | |
| related |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| library-index | Full index of all fragments |
TDQS
Scored across 6 tools
Each tool serves a unique, clearly defined purpose: search, retrieval, browsing, project detection, category listing, and metrics. There is no overlap or ambiguity.
All tool names follow a consistent 'verb_noun' pattern (e.g., search_knowledge, get_fragment), making the API predictable and easy to learn.
With 6 tools, the server is well-scoped for a knowledge management service. Each tool is essential, covering discovery, retrieval, and analysis without bloat or deficiency.
The tool surface covers the full knowledge workflow: project detection, library browsing, searching, fragment retrieval, category overview, and search analytics. No obvious gaps exist for the stated purpose.