Claude Memory MCP Server
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 |
|---|---|
| memory_add_observationA | Record an observation from the current session. Use this to capture discoveries, gotchas, decisions, trade-offs, or problem-solutions that should be remembered across sessions. |
| memory_get_observationA | Retrieve a specific observation by ID. Use this after seeing an observation in the index that looks relevant. |
| memory_search_observationsA | Search observations by keyword. Returns matching observations sorted by recency. |
| memory_get_timelineB | Get observations around a specific point in time. Useful for understanding the context of an observation. |
| memory_get_indexA | Get the progressive disclosure index showing all recent observations. This shows WHAT exists and retrieval COST (tokens) without full details. |
| memory_add_conceptA | Add a concept to the knowledge graph. Concepts represent domain knowledge that can be connected via typed relationships. |
| memory_get_conceptA | Retrieve a specific concept from the knowledge graph. |
| memory_find_solutionsA | Find concepts that solve a problem by traversing 'resolved_by', 'prevents', 'mitigates', or 'enables' relationships. |
| memory_find_relatedA | Find conceptually related concepts via graph traversal (BFS). Finds concepts connected by any relationship type. |
| memory_add_connectionA | Add a relationship between two concepts. Available relationships: resolved_by, prevents, mitigates, causes, enables, requires, depends_on, is_a, part_of, instance_of, contains, precedes, follows, related_to, contrasts_with, similar_to, implemented_by, grounded_in, applies_when |
| memory_get_knowledge_indexA | Get the knowledge graph index showing key insights, problem-solution mappings, and knowledge domains. |
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 11 tools
Tools are largely distinct with clear separation between knowledge graph concepts and observations. However, memory_get_knowledge_index and memory_get_index could be confused, and memory_find_solutions vs memory_find_related serve similar traversal purposes.
All tools follow a consistent memory_ verb_noun pattern (get, find, add, search). The structure is uniform and predictable across both concepts and observations.
11 tools is well within the ideal range and covers the two main domains (knowledge graph and observations) without excessive overlap or redundancy.
Core operations for adding and retrieving concepts, observations, and connections are covered, plus search and index views. Missing update/delete operations, but memory systems often favor append-only, and the lack is a minor gap.