optimized memory mcp server
A persistent memory implementation using a local knowledge graph that lets Claude remember information about users across conversations.
A persistent memory implementation using a local knowledge graph that lets Claude remember information about users across conversations.
This is to test and demonstrate Claude AI's coding abilities, as well as good AI workflows and prompt design. This is a fork of a Python Memory MCP Server (I believe the official one is in Java) which uses SQLite for a backend.
A basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats.
Entities are the primary nodes in the knowledge graph. Each entity has: - A unique name (identifier) - An entity type (e.g., "person", "organization", "event") - A list of observations
Example:
{
"name": "John_Smith",
"entityType": "person",
"observations": ["Speaks fluent Spanish"]
}
Relations define directed connections between entities. They are always stored in active voice and describe how entities interact or relate to each other.
Example:
{
"from": "John_Smith",
"to": "Anthropic",
"relationType": "works_at"
}
Observations are discrete pieces of information about an entity. They are:
Example:
{
"entityName": "John_Smith",
"observations": [
"Speaks fluent Spanish",
"Graduated in 2019",
"Prefers morning meetings"
]
}
entities
(array of objects)name
(string): Entity identifierentityType
(string): Type classificationobservations
(string[]): Associated observationsIgnores entities with existing names
create_relations
relations
(array of objects)from
(string): Source entity nameto
(string): Target entity namerelationType
(string): Relationship type in active voiceSkips duplicate relations
add_observations
observations
(array of objects)entityName
(string): Target entitycontents
(string[]): New observations to addFails if entity does not exist
delete_entities
entityNames
(string[])Silent operation if entity does not exist
delete_observations
deletions
(array of objects)entityName
(string): Target entityobservations
(string[]): Observations to removeSilent operation if observation does not exist
delete_relations
relations
(array of objects)from
(string): Source entity nameto
(string): Target entity namerelationType
(string): Relationship typeSilent operation if relation does not exist
read_graph
Returns complete graph structure with all entities and relations
search_nodes
query
(string)Returns matching entities and their relations
open_nodes
names
(string[])Add this to your claude_desktop_config.json:
{
"mcpServers": {
"memory": {
"command": "docker",
"args": ["run", "-i", "--rm", "mcp/memory"]
}
}
}
{
"mcpServers": {
"memory": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
The prompt for utilizing memory depends on the use case. Changing the prompt will help the model determine the frequency and types of memories created.
Here is an example prompt for chat personalization. You could use this prompt in the "Custom Instructions" field of a Claude.ai Project.
Follow these steps for each interaction:
1. User Identification:
- You should assume that you are interacting with default_user
- If you have not identified default_user, proactively try to do so.
2. Memory Retrieval:
- Always begin your chat by saying only "Remembering..." and retrieve all relevant information from your knowledge graph
- Always refer to your knowledge graph as your "memory"
3. Memory
- While conversing with the user, be attentive to any new information that falls into these categories:
a) Basic Identity (age, gender, location, job title, education level, etc.)
b) Behaviors (interests, habits, etc.)
c) Preferences (communication style, preferred language, etc.)
d) Goals (goals, targets, aspirations, etc.)
e) Relationships (personal and professional relationships up to 3 degrees of separation)
4. Memory Update:
- If any new information was gathered during the interaction, update your memory as follows:
a) Create entities for recurring organizations, people, and significant events
b) Connect them to the current entities using relations
b) Store facts about them as observations
Docker:
docker build -t mcp/memory -f src/memory/Dockerfile .
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.