ctx-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CTX_MEMORY_DB_PATH | No | Override the default database path. | ~/.ctx-memory/store.db |
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 |
|---|---|
| store_messageC | Buffer a conversation message for session-end processing. |
| store_eventC | Record a tool call event (file edit, bash command, etc.) for the current session. |
| search_contextB | Search past sessions for context relevant to a query. Uses embedding similarity, falls back to keyword search. |
| get_project_memoryC | Return the full project memory document (architecture, conventions, recent work, known issues). |
| list_sessionsC | List recent sessions for a project with their goals and outcomes. |
| end_sessionC | Signal session end — runs Layer 1→2→3 pipeline, stores digest, updates project memory. |
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 6 tools
Each tool has a clearly distinct purpose: session lifecycle (end_session), memory retrieval (get_project_memory, list_sessions, search_context), and data recording (store_event, store_message). No overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case, e.g., end_session, get_project_memory, store_event. The naming is predictable and uniform.
With 6 tools, the server covers core memory management operations without bloat. The count is well-scoped for the domain of session context and project memory.
The tool surface covers the full typical lifecycle: recording events/messages, searching and retrieving context, listing sessions, and finalizing sessions with memory updates. No obvious gaps.