recall-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RECALL_MCP_DB | No | Path to SQLite DB file | ~/.recall/memory.db |
| RECALL_LOG_LEVEL | No | DEBUG / INFO / WARNING / ERROR (stderr only) | INFO |
| RECALL_DECAY_DAYS | No | Days at full weight before decay starts | 90 |
| RECALL_MAX_LENGTH | No | Max chars per memory (truncates with notice) | 50000 |
| RECALL_MAX_RESULTS | No | Hard cap on recall and list_memories limits | 50 |
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 |
|---|---|
| rememberA | Store a long-term memory. Use this whenever the user states a preference, decision, fact, or piece of context worth recalling in future sessions. |
| recallA | Semantic search across all stored memories. Use this at the start of a session to recover context from prior sessions. |
| forgetA | Delete a memory by id or by content match (FTS query). |
| list_memoriesC | List memories with optional filters and ordering. |
| summarize_sessionA | Auto-extract memorable facts/preferences/decisions from a list of conversation messages and store them as memories. |
| get_statsB | Return aggregate stats: total, per-project, per-tag, oldest/newest, most-accessed. |
| export_memoriesA | Export all memories (or one project) as a JSON dict. |
| import_memoriesA | Import memories from JSON. on_duplicate: skip | bump | replace. |
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
Each tool has a distinct purpose: remember stores, recall searches, forget deletes, list_memories enumerates, summarize_session derives memories from conversation, get_stats aggregates statistics, and export/import handle data transfer. No two tools overlap in their core function, making misselection unlikely.
Tool names follow a consistent imperative verb pattern: either bare verbs (remember, recall, forget) or verb_noun pairs (list_memories, summarize_session, get_stats, export_memories, import_memories). The convention is uniform and predictable, with no mixed casing or inconsistent verb styles.
Eight tools is a well-scoped set for a memory management server. Each tool addresses a core need (store, search, delete, list, auto-summarize, stats, export, import) without redundancy or bloat, fitting comfortably in the ideal 3–15 range.
The tool surface covers the full memory lifecycle: creating (remember, summarize_session, import_memories), reading (recall, list_memories, get_stats, export_memories), updating (import_memories with replace/bump), and deleting (forget). No critical operations are missing for managing persisted memories.