memory-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | No | Anthropic API key for the Haiku-based extractor. Resolved from environment variable, or else from config files. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_initA | Initialize project memory with name and description. |
| memory_saveA | Save a memory about this project. Records decisions, patterns, architecture, gotchas, progress, or context for future sessions. |
| memory_recallA | Recall all active memories, optionally filtered by type or tags. |
| memory_deleteB | Delete a specific memory by ID. |
| memory_searchB | Search memories by keyword. Returns ranked results matching the query across content and tags. |
| memory_relatedA | Get all memories related to specific tags/areas. Use to explore a topic in depth. |
| memory_askA | Ask a question and get an answer synthesized from project memories. Like RAG over your project knowledge. |
| memory_consolidateA | Manually trigger memory consolidation. Merges duplicates, removes outdated memories, keeps memory sharp. |
| memory_consciousnessA | Generate the full consciousness document. This is what gets written to CLAUDE.md. |
| memory_statsA | Show memory statistics: counts by type, active/archived/superseded, last consolidation. |
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 10 tools
Most tools have distinct purposes, but the retrieval tools (recall, search, related, ask) overlap conceptually. However, each has a clear differentiator: recall lists all, search ranks by keyword, related explores by tag, ask synthesizes an answer. No two tools are truly indistinguishable.
All tools share the 'memory_' prefix, but suffixes mix verbs (save, delete, search) with nouns (related, consciousness, stats). This inconsistency is noticeable but the command pattern is still readable.
10 tools is well within the ideal range for a focused domain. Each tool addresses a distinct aspect of memory management without bloat.
The core memory lifecycle (init, save, recall, delete, consolidate) is covered, plus useful extras (search, ask, related, stats). Missing an explicit update tool, but delete+re-save works around it.