Knowledge Graph Memory Server
Knowledge Graph Memory Server
A basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats and learn from past errors through a lesson system.
Core Concepts
Entities
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:
Relations
Relations define directed connections between entities. They are always stored in active voice and describe how entities interact or relate to each other.
Example:
Observations
Observations are discrete pieces of information about an entity. They are:
- Stored as strings
- Attached to specific entities
- Can be added or removed independently
- Should be atomic (one fact per observation)
Example:
Lessons
Lessons are special entities that capture knowledge about errors and their solutions. Each lesson has:
- A unique name (identifier)
- Error pattern information (type, message, context)
- Solution steps and verification
- Success rate tracking
- Environmental context
- Metadata (severity, timestamps, frequency)
Example:
API
Tools
- create_entities
- Create multiple new entities in the knowledge graph
- Input:
entities
(array of objects)- Each object contains:
name
(string): Entity identifierentityType
(string): Type classificationobservations
(string[]): Associated observations
- Each object contains:
- Ignores entities with existing names
- create_relations
- Create multiple new relations between entities
- Input:
relations
(array of objects)- Each object contains:
from
(string): Source entity nameto
(string): Target entity namerelationType
(string): Relationship type in active voice
- Each object contains:
- Skips duplicate relations
- add_observations
- Add new observations to existing entities
- Input:
observations
(array of objects)- Each object contains:
entityName
(string): Target entitycontents
(string[]): New observations to add
- Each object contains:
- Returns added observations per entity
- Fails if entity doesn't exist
- delete_entities
- Remove entities and their relations
- Input:
entityNames
(string[]) - Cascading deletion of associated relations
- Silent operation if entity doesn't exist
- delete_observations
- Remove specific observations from entities
- Input:
deletions
(array of objects)- Each object contains:
entityName
(string): Target entityobservations
(string[]): Observations to remove
- Each object contains:
- Silent operation if observation doesn't exist
- delete_relations
- Remove specific relations from the graph
- Input:
relations
(array of objects)- Each object contains:
from
(string): Source entity nameto
(string): Target entity namerelationType
(string): Relationship type
- Each object contains:
- Silent operation if relation doesn't exist
- read_graph
- Read the entire knowledge graph
- No input required
- Returns complete graph structure with all entities and relations
- search_nodes
- Search for nodes based on query
- Input:
query
(string) - Searches across:
- Entity names
- Entity types
- Observation content
- Returns matching entities and their relations
- open_nodes
- Retrieve specific nodes by name
- Input:
names
(string[]) - Returns:
- Requested entities
- Relations between requested entities
- Silently skips non-existent nodes
Lesson Management Tools
- create_lesson
- Create a new lesson from an error and its solution
- Input:
lesson
(object)- Contains:
name
(string): Unique identifierentityType
(string): Must be "lesson"observations
(string[]): Notes about the error and solutionerrorPattern
(object): Error detailstype
(string): Category of errormessage
(string): Error messagecontext
(string): Where error occurredstackTrace
(string, optional): Stack trace
metadata
(object): Additional informationseverity
("low" | "medium" | "high" | "critical")environment
(object): System detailsfrequency
(number): Times encounteredsuccessRate
(number): Solution success rate
verificationSteps
(array): Solution verification- Each step contains:
command
(string): Action to takeexpectedOutput
(string): Expected resultsuccessIndicators
(string[]): Success markers
- Each step contains:
- Contains:
- Automatically initializes metadata timestamps
- Validates all required fields
- find_similar_errors
- Find similar errors and their solutions
- Input:
errorPattern
(object)- Contains:
type
(string): Error categorymessage
(string): Error messagecontext
(string): Error context
- Contains:
- Returns matching lessons sorted by success rate
- Uses fuzzy matching for error messages
- update_lesson_success
- Update success tracking for a lesson
- Input:
lessonName
(string): Lesson to updatesuccess
(boolean): Whether solution worked
- Updates:
- Success rate (weighted average)
- Frequency counter
- Last update timestamp
- get_lesson_recommendations
- Get relevant lessons for current context
- Input:
context
(string) - Searches across:
- Error type
- Error message
- Error context
- Lesson observations
- Returns lessons sorted by:
- Context relevance
- Success rate
- Includes full solution details
File Management
The server now handles two types of files:
memory.json
: Stores basic entities and relationslesson.json
: Stores lesson entities with error patterns
Files are automatically split if they exceed 1000 lines to maintain performance.
Cursor MCP Client Setup
To integrate this memory server with Cursor MCP client, follow these steps:
- Clone the Repository:
- Install Dependencies:
- Build the Project:
- Configure the Server:
- Locate the full path to the built server file:
/path/to/the/dist/index.js
- Start the server using Node.js:
node /path/to/the/dist/index.js
- Activate in Cursor:
- Use the keyboard shortcut
Ctrl+Shift+P
- Type "reload window" and select it
- Wait a few seconds for the MCP server to activate
- Select the stdio type when prompted
The memory server should now be integrated with your Cursor MCP client and ready to use.
Usage with Claude Desktop
Setup
Add this to your claude_desktop_config.json:
Docker
NPX
NPX with custom setting
The server can be configured using the following environment variables:
MEMORY_FILE_PATH
: Path to the memory storage JSON file (default:memory.json
in the server directory)
System Prompt
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.
Building
Docker:
License
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.
New Tools
- create_lesson
- Create a new lesson from an error and its solution
- Input:
lesson
(object)- Contains error pattern, solution steps, and metadata
- Automatically tracks creation time and updates
- Verifies solution steps are complete
- find_similar_errors
- Find similar errors and their solutions
- Input:
errorPattern
(object)- Contains error type, message, and context
- Returns matching lessons sorted by success rate
- Includes related solutions and verification steps
- update_lesson_success
- Update success tracking for a lesson
- Input:
lessonName
(string): Lesson to updatesuccess
(boolean): Whether solution worked
- Updates success rate and frequency metrics
- get_lesson_recommendations
- Get relevant lessons for current context
- Input:
context
(string) - Returns lessons sorted by relevance and success rate
- Includes full solution details and verification steps
BIG CREDITS TO THE OWNER OF THIS REPO FOR THE BASE CODE I ENHANCED IT WITH LESSONS AND FILE MANAGEMENT
Big thanks! https://github.com/modelcontextprotocol/servers jerome3o-anthropic https://github.com/modelcontextprotocol/servers/tree/main/src/memory
You must be authenticated.
Enhances user interaction through a persistent memory system that remembers information across chats and learns from past errors by utilizing a local knowledge graph and lesson management.