recall
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RECALL_MEMORY_DIR | No | Where memory files are stored | ~/.recall/memories |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recall_writeA | Create a new memory, or replace an existing one only when you explicitly allow it. Persists one atomic fact as a Markdown file. This is safe by default: if a memory with the same name already exists, the write is refused and a conflict is returned, so a durable memory is never overwritten by accident. Pass overwrite: true to replace it on purpose. [[wikilink]] references in the body are detected automatically and exposed via recall_links. Args:
Returns the stored memory and whether it was 'created' or 'updated', or a 'conflict' if a memory with that name already exists and overwrite is false. |
| recall_getA | Fetch a single memory by name, including its full body. Args:
Returns the memory, or a not-found message if no memory has that name. |
| recall_searchA | Recall memories relevant to a free-text query, ranked by relevance. This is the primary retrieval tool. It scores every memory against the query (a hit in the name outweighs the description, which outweighs the body), drops non-matches, and returns the best results first. Args:
Returns ranked matches with their relevance scores. Empty if nothing matches. |
| recall_listA | List stored memories (index view, no bodies), optionally filtered by type. Args:
Returns memory summaries plus pagination metadata. |
| recall_linksA | Find memories connected to a given memory through [[wikilink]] references. Args:
Returns the names of connected memories in each requested direction. |
| recall_deleteA | Permanently delete a memory by name. Args:
Returns whether a memory was deleted. Deleting a non-existent memory is a safe no-op (returns deleted: false). This action cannot be undone. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/andrewhomeyer/recall-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server