Cortex
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | No | The database URL for PostgreSQL with pgvector | postgresql://localhost:5432/cortex |
| CORTEX_USE_ASSEMBLER | No | Enable structured context assembly for retrieval (e.g., set to '1' for BEAM benchmark) |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_methodologyA | Returns the user's cognitive profile for the current domain. Pre-computed, <50ms. Use at session start for context injection. |
| detect_domainB | Lightweight domain classification from cwd, project, or first message. <20ms. |
| rebuild_profilesB | Full rescan of all session data to rebuild methodology profiles. <10s. |
| list_domainsB | Overview of all detected cognitive domains. <10ms. |
| record_session_endC | Incremental profile update after a session ends. <200ms. |
| get_methodology_graphB | Returns methodology map as graph data for 3D visualization. <100ms. |
| open_visualizationB | Launch the unified 3D neural graph in the browser. Combines methodology profiles, memories, and knowledge graph. |
| explore_featuresC | Explore interpretability features: dictionary features, attribution graphs, persona vectors, and cross-domain behavioral persistence. Inspired by Anthropic's mechanistic interpretability research. |
| run_pipelineC | Drive the ai-architect pipeline end-to-end: discovery -> impact -> strategy -> PRD -> verification -> implementation -> PR. Connects to ai-architect MCP server over stdio. |
| rememberD | Store a memory through the predictive coding write gate. |
| recallC | Retrieve memories using intent-adaptive PG recall with production enrichments. |
| memory_statsC | Memory system diagnostics: counts, heat distribution, entities, triggers. |
| checkpointC | Hippocampal replay: save/restore working state across context compaction events. |
| narrativeC | Generate a project narrative/story from stored memories for a directory or domain. |
| consolidateB | Run memory maintenance: heat decay, compression, and CLS consolidation cycles. |
| import_sessionsB | Import conversation history from ~/.claude/projects/ into the memory store. Extracts decisions, errors, architecture notes, and key insights from JSONL sessions. |
| forgetA | Delete a memory by ID. Supports soft (mark stale) or hard (permanent) deletion. Protected memories require force=True. |
| validate_memoryB | Validate memories against current filesystem state. Marks stale memories whose referenced files no longer exist. |
| rate_memoryB | Rate a memory as useful or not. Drives metamemory confidence which affects decay resistance and recall ranking. |
| seed_projectC | Bootstrap memory from an existing codebase. Analyzes structure, config, docs, entry points, and CI/CD. Stores key discoveries as memories. |
| anchorA | Mark a memory as compaction-resistant. Anchored memories survive context compaction, heat decay, and cannot be deleted without force. Use for critical facts and active decisions. |
| backfill_memoriesA | Auto-import prior Claude Code conversations into the memory store. Idempotent -- tracks already-processed session files by hash. Links historical work to core concepts automatically. |
| codebase_analyzeA | Analyze a codebase and store its structure as Cortex memories. Uses tree-sitter AST for cross-file resolution, call graphs, and community detection. Incremental: only processes changed files. |
| recall_hierarchicalA | Retrieve memories using the fractal hierarchy (L0/L1/L2 clusters). Adaptive weighting based on query length — short queries search broad, long queries search specific. |
| drill_downC | Navigate into a fractal memory cluster. L2 cluster → shows L1 child clusters. L1 cluster → shows individual memories. |
| navigate_memoryB | Navigate memory space using Successor Representation (co-access patterns). Starting from a memory ID, returns co-accessed neighbors and their SR distances. |
| get_causal_chainC | Trace entity relationships through the knowledge graph. Returns causal/dependency chains from a starting entity or memory. |
| detect_gapsB | Identify knowledge gaps in the memory store: isolated entities, sparse domains, temporal drift, and low-heat topic clusters. |
| sync_instructionsB | Sync top memory insights into CLAUDE.md for the project directory. Adds or refreshes a '## Memory Insights' section. |
| create_triggerB | Create a prospective memory trigger: a future-oriented reminder that fires when a condition is met (keyword, time, file, or domain). |
| add_ruleC | Add a neuro-symbolic rule to the memory store. Rules hard-filter or soft-rerank recall results based on conditions. |
| get_rulesB | List active neuro-symbolic rules in the memory store, optionally filtered by scope or rule type. |
| get_project_storyC | Generate a period-based autobiographical narrative of project activity. Returns chronological 'chapters' of what happened during a time period. |
| assess_coverageC | Evaluate knowledge coverage completeness for a project directory. Returns a 0-100 coverage score and actionable recommendations. |
| wiki_writeA | Author a wiki page (adr/specs/files/notes) or append/replace an existing one. Pages live under ~/.claude/methodology/wiki/ and are indexed in PostgreSQL as protected pointer memories for recall. |
| wiki_readA | Read the raw markdown of a wiki page by its relative path. |
| wiki_listB | List authored wiki pages. Optionally filter by kind (adr/specs/files/notes). |
| wiki_linkA | Add a bidirectional link between two wiki pages. Updates the Related section of both files. Idempotent. |
| wiki_adrC | Create a numbered ADR (architecture decision record) from structured fields. Auto-increments the ADR number. |
| wiki_reindexA | Regenerate the wiki table of contents at .generated/INDEX.md. Authored pages are never touched. |
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 40 tools
The tools cover distinct functional areas (memory management, wiki operations, methodology analysis, etc.), but there is some overlap that could cause confusion. For example, 'recall' and 'recall_hierarchical' both retrieve memories with different algorithms, and 'backfill_memories' and 'import_sessions' both import conversation history, which might lead to misselection by an agent without careful reading of descriptions.
Most tools follow a consistent verb_noun or verb_adjective_noun pattern (e.g., 'add_rule', 'anchor', 'assess_coverage'), with clear and descriptive names. However, there are minor deviations like 'wiki_adr' (which mixes a prefix with an acronym) and 'run_pipeline' (which is less structured), slightly reducing consistency.
With 40 tools, the count is excessive for a single server, making it heavy and potentially overwhelming for agents to navigate. While the domain (cognitive memory and project management) is broad, the toolset feels bloated with many specialized operations that could have been grouped or streamlined, indicating poor scoping.
The tool set provides comprehensive coverage for memory storage, retrieval, maintenance, wiki management, and project analysis, with clear CRUD and lifecycle operations (e.g., 'remember', 'recall', 'forget', 'validate_memory'). There are no obvious gaps; it supports end-to-end workflows from data ingestion to visualization and narrative generation.