cortexmem
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CORTEXMEM_MODEL | No | Model identifier used for compaction | claude-haiku-4-5-20251001 |
| ANTHROPIC_API_KEY | No | Optional API key to enable LLM-based session compaction via summarize_session | |
| CORTEXMEM_MAX_TOKENS | No | Default maximum tokens for get_context | 3000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_contextA | Save context to persistent memory. Call this whenever you make a decision, discover something non-obvious about the codebase, agree on a constraint with the user, note WIP state, or learn a coding preference. Saved context persists across sessions and editors. Call proactively — future sessions depend on what you save now. |
| get_contextA | Retrieve persistent memory from previous sessions. Call at session start with no arguments to get the context pyramid: project overview, current branch summary, and recent session summaries — all in ~500-800 tokens. Use with a query to do hierarchical search: matches project → branch → session summaries first, then drills into raw chunks only when needed. Use depth to control how deep to search. Always call this first in a new session. |
| summarize_sessionA | Compact and persist session memory into the context pyramid. Creates a session summary from saved context, rolls it up into a branch summary, then updates the project overview. Call at end of session. Works best with ANTHROPIC_API_KEY for LLM-powered compaction; falls back to deterministic summarization without it. |
| get_statusB | Quick stats on cortexmem: total chunks stored, breakdown by type, storage location, last init time, last indexed commit. |
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 4 tools
Each tool targets a distinct phase of the memory lifecycle: save_context writes raw chunks, get_context reads/search, summarize_session compacts, and get_status reports stats. The only mild overlap is that both save_context and summarize_session persist data, but the descriptions clearly differentiate raw chunks from session summaries.
All tool names use a consistent snake_case verb_noun pattern: save_context, get_status, get_context, summarize_session. The verbs (save, get, summarize) are standard and predictable.
Four tools is a well-scoped, minimal set for a persistent memory server. Each tool maps to a distinct operation (write, read, summarize, status), and none feels redundant or missing at the count level.
The surface covers saving, retrieving, summarizing, and status reporting for persistent memory. However, it lacks an explicit delete/forget or edit operation, so agents cannot easily prune stale or incorrect memories — a minor but real gap.