Deep Recall MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPRECALL_API_KEY | Yes | Your Deep Recall API key |
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": false
} |
| prompts | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deeprecall_rememberA | Store a memory. Behind the scenes: embeds for semantic search, builds graph edges to related memories, detects contradictions, auto-resolves temporal changes, infers entity relationships, and periodically consolidates episode clusters into durable facts. All biology runs automatically — just store what matters. |
| deeprecall_searchA | Search memories. Hybrid keyword + semantic search, ranked by salience. Faded memories rank lower. 'outdoor activities' finds 'loves hiking'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| deeprecall_instructions | Instructions for the AI on how to use Deep Recall memory tools proactively |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are clearly distinct: one stores a memory, the other searches memories. There is no overlap or ambiguity in their purposes.
Both tools follow a consistent verb_noun pattern with the 'deeprecall_' prefix, using 'remember' and 'search' as clear action verbs.
With only 2 tools, the server feels minimal. While it covers basic store and search, it lacks additional tools for management, making the count borderline for a memory system.
The server lacks common operations like delete, update, or list memories. Although it claims automatic resolution, agents may need explicit lifecycle tools, leaving significant gaps.