Memory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_MCP_DB | No | Override the default database location (~/.memory_mcp/memory.db) | |
| MEMORY_MCP_SOURCES | No | Extend session sources with additional directories (format: type:path;type:path) |
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_memoryA | Save a note to persistent memory. Use this to remember important context, decisions, patterns, or user preferences across sessions. |
| search_memoryA | Search saved memories. Use short keywords, not natural language phrases — each word is matched independently and ranked by relevance. |
| list_memoriesB | List recent saved memories, optionally filtered by tag. |
| delete_memoryB | Delete a specific memory by its ID. |
| list_sessionsB | List recent AI coding sessions. Filter by source ('claude_code' or 'omp') or by project path substring. |
| get_sessionB | Retrieve the conversation from a specific session. Shows the full message flow including user messages, assistant responses, and tool usage. |
| search_sessionsB | Search across all session messages. Use short keywords, not natural language phrases — each word is matched independently and ranked by relevance. |
| refresh_sessionsA | Scan for new or updated session files and index them. Run this if recent sessions aren't showing up in search results. |
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 clearly distinct purpose with no overlap: delete_memory removes a memory, get_session retrieves a session's conversation, list_memories lists memories, list_sessions lists sessions, refresh_sessions indexes new sessions, save_memory stores a memory, search_memory searches memories, and search_sessions searches sessions. The descriptions reinforce these distinct roles, making misselection unlikely.
All tools follow a consistent verb_noun pattern using snake_case: delete_memory, get_session, list_memories, list_sessions, refresh_sessions, save_memory, search_memory, and search_sessions. This predictable naming scheme enhances readability and usability across the toolset.
With 8 tools, the server is well-scoped for managing memories and sessions. Each tool serves a clear purpose, such as CRUD operations for memories (save, list, search, delete) and sessions (list, get, search, refresh), avoiding bloat while covering essential functionality for the domain.
The toolset provides strong coverage for memory and session management, including create (save_memory), read (list_memories, get_session), delete (delete_memory), and search (search_memory, search_sessions). A minor gap exists in updating memories or sessions, but agents can work around this by deleting and re-saving, and the refresh_sessions tool handles session updates indirectly.