Graphiti-Memory MCP Server
Provides memory and knowledge graph operations using Neo4j database, including adding memories, searching entities and relationships, managing episodes, and querying historical data through natural language interfaces.
Optional integration for enhanced entity extraction from memories and episodes stored in the knowledge graph.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Graphiti-Memory MCP Server add memory about our team meeting where we decided to prioritize the AI roadmap"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Graphiti-Memory MCP Server
A Model Context Protocol (MCP) server that provides memory and knowledge graph operations using Neo4j and the Graphiti framework.
Features
📝 Add Memories: Store episodes and information in the knowledge graph with automatic entity extraction
🧠 Search Nodes: Query entities in your knowledge graph using natural language
🔗 Search Facts: Find relationships and connections between entities
📚 Retrieve Episodes: Get historical episodes and memories
🗑️ Management Tools: Delete episodes, edges, and clear the graph
🤖 AI-Powered: Optional OpenAI integration for enhanced entity extraction
📊 Real-time Data: Direct connection to your Neo4j database
🛠️ Built-in Diagnostics: Comprehensive error messages and troubleshooting
Related MCP server: Graphiti Knowledge Graph MCP Server
Installation
Prerequisites
Neo4j Database: You need a running Neo4j instance
# Install Neo4j (via Homebrew on macOS) brew install neo4j # Start Neo4j neo4j startPython 3.10+: Required for the MCP server
Install from PyPI
pip install graphiti-memoryInstall from Source
git clone https://github.com/alankyshum/graphiti-memory.git
cd graphiti-memory
pip install -e .Configuration
MCP Configuration
Add to your MCP client configuration file (e.g., Claude Desktop config):
{
"mcpServers": {
"graphiti-memory": {
"command": "graphiti-mcp-server",
"env": {
"NEO4J_URI": "neo4j://127.0.0.1:7687",
"NEO4J_USER": "neo4j",
"NEO4J_PASSWORD": "your-password-here",
"OPENAI_API_KEY": "your-openai-key-here",
"GRAPHITI_GROUP_ID": "default"
}
}
}
}Neo4j Setup
Set Password (first-time setup):
neo4j-admin dbms set-initial-password YOUR_PASSWORDTest Connection:
# HTTP interface curl http://127.0.0.1:7474 # Bolt protocol nc -zv 127.0.0.1 7687
Available Tools
1. add_memory
Add an episode or memory to the knowledge graph. This is the primary way to add information.
Example:
{
"name": "add_memory",
"arguments": {
"name": "Project Discussion",
"episode_body": "We discussed the new AI feature roadmap for Q2. Focus on improving entity extraction.",
"source": "text",
"group_id": "project-alpha"
}
}Parameters:
name: Name of the episode (required)episode_body: Content to store - text, message, or JSON (required)source: Type of content - "text", "message", or "json" (default: "text")group_id: Optional namespace for organizing datasource_description: Optional description
2. search_memory_nodes
Search for nodes (entities) in the knowledge graph using natural language.
Example:
{
"name": "search_memory_nodes",
"arguments": {
"query": "machine learning",
"max_nodes": 10
}
}Returns: List of nodes with UUID, name, summary, labels, and timestamps.
3. search_memory_facts
Search for facts (relationships) between entities in the knowledge graph.
Example:
{
"name": "search_memory_facts",
"arguments": {
"query": "what technologies are related to AI",
"max_facts": 10
}
}Returns: List of fact triples with source, target, and relationship details.
4. get_episodes
Retrieve recent episodes for a specific group.
Example:
{
"name": "get_episodes",
"arguments": {
"group_id": "project-alpha",
"last_n": 10
}
}5. delete_episode
Delete an episode from the knowledge graph.
Example:
{
"name": "delete_episode",
"arguments": {
"uuid": "episode-uuid-here"
}
}6. delete_entity_edge
Delete a fact (entity edge) from the knowledge graph.
Example:
{
"name": "delete_entity_edge",
"arguments": {
"uuid": "edge-uuid-here"
}
}7. get_entity_edge
Retrieve a specific entity edge by UUID.
Example:
{
"name": "get_entity_edge",
"arguments": {
"uuid": "edge-uuid-here"
}
}8. clear_graph
Clear all data from the knowledge graph (DESTRUCTIVE).
Example:
{
"name": "clear_graph",
"arguments": {}
}Usage
With Claude Desktop
Configure in ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"graphiti-memory": {
"command": "graphiti-mcp-server",
"env": {
"NEO4J_URI": "neo4j://127.0.0.1:7687",
"NEO4J_USER": "neo4j",
"NEO4J_PASSWORD": "your-password",
"OPENAI_API_KEY": "your-openai-key-here",
"GRAPHITI_GROUP_ID": "default"
}
}
}
}Note: OPENAI_API_KEY is optional. Without it, entity extraction will be limited but the server will still work.
Standalone Testing
Test the server directly from command line:
export NEO4J_URI="neo4j://127.0.0.1:7687"
export NEO4J_USER="neo4j"
export NEO4J_PASSWORD="your-password"
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}' | graphiti-mcp-serverTroubleshooting
Connection Failed
Error: Connection refused or ServiceUnavailable
Solutions:
Check Neo4j is running:
neo4j statusStart Neo4j:
neo4j startVerify port 7687 is accessible:
nc -zv 127.0.0.1 7687
Authentication Failed
Error: Unauthorized or authentication failure
Solutions:
Verify password is correct
Reset password:
neo4j-admin dbms set-initial-password NEW_PASSWORDUpdate password in MCP configuration
Use test tool to verify:
test_neo4j_auth
Package Not Found
Error: neo4j package not installed
This package automatically installs the neo4j dependency. If you see this error:
pip install neo4jDevelopment
Setup Development Environment
git clone https://github.com/alankyshum/graphiti-memory.git
cd graphiti-memory
pip install -e ".[dev]"Running Tests
# Test the server
python -m graphiti_memory.server << 'EOF'
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}
EOFArchitecture
MCP Client (Claude Desktop / Cline / etc.)
↓
Graphiti-Memory Server
↓
Neo4j DatabaseThe server:
Listens on stdin for JSON-RPC messages
Logs diagnostics to stderr
Responds on stdout with JSON-RPC
Maintains persistent Neo4j connection
Contributing
Contributions welcome! Please:
Fork the repository
Create a feature branch
Make your changes
Submit a pull request
License
MIT License - see LICENSE file for details.
Links
Issues: https://github.com/alankyshum/graphiti-memory/issues
MCP Specification: https://modelcontextprotocol.io
Credits
Built for use with:
Graphiti - Knowledge graph framework
Available Tools
8 toolsadd_memoryC
Add an episode/memory to the knowledge graph. This is the primary way to add information.
Inputs: name (required), episode_body (required), group_id, source, +1 more.
clear_graphA
Clear all data from the knowledge graph (DESTRUCTIVE)
Inputs: no named parameters.
delete_entity_edgeC
Delete an entity edge (fact) from the knowledge graph
Inputs: uuid (required).
delete_episodeC
Delete an episode from the knowledge graph
Inputs: uuid (required).
get_entity_edgeB
Get an entity edge by UUID
Inputs: uuid (required).
get_episodesC
Get recent episodes for a group
Inputs: group_id, last_n.
search_memory_factsC
Search for facts (relationships) in the knowledge graph
Inputs: query (required), group_ids, max_facts.
search_memory_nodesC
Search for nodes (entities) in the knowledge graph
Inputs: query (required), group_ids, max_nodes.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Most tools have distinct purposes, such as add_memory for adding, clear_graph for clearing, and search_memory_facts for searching facts. However, get_entity_edge and search_memory_nodes could be slightly ambiguous since both involve retrieving entity-related information, but their descriptions clarify the difference (specific vs. search).
The naming follows a consistent verb_noun pattern with snake_case throughout, such as add_memory and delete_episode. There are minor deviations like get_entity_edge using 'entity_edge' instead of a more uniform term like 'fact', but overall the pattern is clear and predictable.
With 8 tools, the count is well-scoped for a memory/knowledge graph server, covering core operations like add, delete, get, search, and clear. Each tool serves a distinct function without bloat, making it manageable and purposeful for the domain.
The tool set provides good coverage for a knowledge graph domain, including add, delete, get, and search operations for episodes and entities. A minor gap is the lack of update tools for modifying existing memories or entities, but agents can work around this by deleting and re-adding, and core workflows are supported.
Related MCP Connectors
Persistent knowledge graph for AI agents. Remember, recall, and forget facts.
Shared long-term memory for AI agents: save and recall context as a searchable knowledge graph.
Long-term memory for your AI as a private knowledge graph: facts, people, links, sources.
Shared memory for AI agents, as a graph in your own Postgres. Writes never call an LLM.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables storage and retrieval of knowledge in a graph database format, allowing users to create, update, search, and delete entities and relationships in a Neo4j-powered knowledge graph through natural language.5-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to build and query temporally-aware knowledge graphs from conversations and data. Supports adding episodes, searching entities and facts, and maintaining persistent memory across interactions.11Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides persistent memory capabilities through Neo4j graph database integration, allowing storage and retrieval of interconnected knowledge with complex relationships between entities. Enables long-term retention and querying of information across multiple conversations through graph-based memory management.1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to store, retrieve, and connect information in a Neo4j graph database as persistent memory, with semantic relationships, natural language search, and temporal tracking across conversations.9150 npm67MIT