Memory Server MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| save_memoryC | Save a value with a key to memory, optionally with tags and expiration |
| recall_memoryB | Retrieve a value by key from memory, with optional related memories |
| list_memoriesB | List all memory keys, optionally filtered by tag |
| delete_memoryC | Delete a memory by key |
| list_all_tagsA | List all unique tags used across all memories |
| search_memory_contentC | Search memory content using fuzzy search |
| link_memoriesC | Create a link between two memories with a relationship type |
| get_linked_memoriesC | Get all memories linked from a source memory |
| find_related_memoriesC | Find memories related to a given memory through content, tags, or links |
| find_memory_pathB | Find the shortest path between two memories through their links |
| search_by_relationshipC | Search for memories based on relationship patterns |
| find_memories_within_degreesC | Find all memories within N degrees of separation from a starting memory |
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 12 tools
Most tools have distinct purposes, but there is some overlap between 'find_related_memories' and 'search_by_relationship', as both involve relationship-based queries, which could cause confusion. Other tools like 'recall_memory' and 'get_linked_memories' are clearly differentiated, with the former retrieving a single memory and the latter focusing on linked connections.
All tool names follow a consistent snake_case pattern with clear verb_noun structures, such as 'delete_memory', 'save_memory', and 'search_memory_content'. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 12 tools, the count is well-suited for a memory management server, covering core operations like save, recall, delete, search, and linking. Each tool serves a specific function without redundancy, making the set comprehensive yet manageable for its domain.
The tool set provides complete coverage for memory management, including CRUD operations (save, recall, delete, list), advanced features like linking, searching by content and relationships, and utility functions such as tag listing. There are no obvious gaps, supporting a full lifecycle from creation to complex queries.