cc-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | No | Preferred credential; falls through to the Claude Code OAuth token when absent or dead | |
| CLAUDE_PROJECT_DIR | No | Consulted by the project-root resolver when it names a directory in the ancestor chain | |
| CC_MEMORY_LOG_LEVEL | No | Log verbosity under ~/.claude/hooks/cc-memory/logs/: DEBUG, INFO (default), WARN, ERROR or SILENT; an unknown value means INFO | INFO |
| CC_MEMORY_PLAN_ENFORCE | No | Kill switch for Stop-hook plan enforcement; set to 0 to switch plan enforcement off entirely | 1 |
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 |
|---|---|
| memory_searchA | Search project memories using full-text search. Returns compact results — use memory_get_details for full content. |
| memory_get_detailsB | Get full details of ACTIVE memories by IDs. Superseded / archived rows are never returned; requested ids that did not resolve come back in "missing". |
| memory_addC | Add a memory via the anti-patch upsert path (merge / supersede / insert depending on similarity to existing). |
| memory_statsC | Get project memory statistics. |
| memory_topicsA | List topic summaries for the project, newest first. Bounded: at most |
| memory_recentC | Get recent memories with optional filters. |
| progress_getC | Read the current PROGRESS.md state (structured fields). |
| progress_regenerateB | Force-rewrite .ccm/PROGRESS.md from the SQL state. |
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 8 tools
Search, recent, and topics all retrieve memories but differ by mode (full-text, recency, topic summaries), and descriptions clarify compact vs full details. Some overlap between memory_recent and memory_search could cause occasional misselection.
All tools use snake_case with consistent domain prefixes (memory_, progress_), and no mixed conventions. The pattern is predictable and readable.
8 tools is well-scoped for a memory plus progress management server, with each tool serving a distinct purpose. No tools feel redundant or missing at the count level.
Covers create (add with upsert), read (search, get details, recent, topics, stats), and progress read/regenerate, but lacks an explicit delete or archive operation. Agents can work around this via supersede behavior in memory_add.