cortex-local-memory
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cortex_code_searchA | Search code with file:line results. Filters by language or path, useful for locating a function or symbol definition. |
| cortex_contextC | Assemble relevant information within a specific token budget limit strictly |
| cortex_healthA | Check if the cortex server is healthy and responsive. Returns system status, document count, and uptime. |
| cortex_mapA | Get a map of the local knowledge base: document count, file type breakdown and sample paths. Use this first when you do not know what is indexed. |
| cortex_memory_batchA | Write multiple memory entries in a single call (max 50), for storing a batch of facts at the end of a session. |
| cortex_memory_deleteC | Delete a memory entry from the cortex knowledge base by its ID |
| cortex_memory_delete_batchB | Delete multiple memory entries from the cortex knowledge base by their IDs |
| cortex_memory_searchC | Search memory entries in the cortex knowledge base |
| cortex_memory_writeB | Write a memory entry to the cortex knowledge base for persistent storage |
| cortex_planA | Given a question or task, return a concrete retrieval plan (which queries to run, which mode, what to look for). Does not itself search. |
| cortex_project_contextA | Collect context scoped to a project directory: matching documents, chunks and file entry points under that path. |
| cortex_searchB | Search the local knowledge base (cortex) using vector and fts and return relevant chunks |
| cortex_statsB | Return Cortex statistics: documents, chunks, vectors, storage usage, current plan and its limits. |
| cortex_suggestB | Get smart search suggestions based on partial query and current context. Returns instant results from prefetched cache or fast search. |
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 14 tools
Search tools are cleanly separated by target: cortex_search (knowledge base), cortex_memory_search (memories), and cortex_code_search (code with file:line). The main overlap is among the three overview/status tools — cortex_health, cortex_stats, and cortex_map all return counts and status information — and between cortex_context and cortex_project_context, though the descriptions differentiate them well enough.
All 14 tools share a uniform cortex_ prefix and snake_case, with a coherent cortex_memory_* family covering write/batch/write/delete/delete_batch/search. The only deviation is that top-level tools use single nouns (map, plan, stats, health) while the memory family uses resource_verb, but the grouping is predictable rather than chaotic.
14 tools sit comfortably in the well-scoped range and each one serves a distinct retrieval, memory-management, or introspection function. No tool looks redundant filler; the memory batch/delete_batch variants correspond to real bulk needs.
Memory operations cover write, batch write, search, delete, and batch delete, and the knowledge base side covers search, code search, planning, context assembly, and introspection. However, there is no memory update/edit or direct get-by-id/list operation, so retrieving a specific known memory relies entirely on search, and no tool apparently indexes documents, implying ingestion happens elsewhere.