MemMCP
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recall_memoriesA | Recall relevant memories using hybrid search (semantic similarity + keyword search). |
| store_memoryA | Store a single memory, automatically generating unique keys and updating indices. |
| store_memories_batchA | Store multiple memories atomically in a single transaction, then rebuild the index once. |
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 3 tools
The three tools are clearly distinct: recall_memories retrieves, store_memory stores a single item, and store_memories_batch stores multiple items atomically. The batch variant is clearly differentiated from the single-store tool by its transactional and batched nature.
All tool names follow a consistent verb_noun pattern: recall_memories, store_memory, store_memories_batch. The verbs are clear and the nouns are consistent, with the batch variant appropriately qualified.
With only 3 tools, the set is tightly scoped for a memory server. Each tool serves a distinct core operation (recall, store single, store batch) without unnecessary bloat, making the count appropriate for its stated purpose.
The server covers the essential store and recall operations, including an efficient batch store. However, it lacks explicit delete or update capabilities, which could be considered a minor gap for a complete memory lifecycle, though not critical for basic use.