Graphiti-Memory MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEO4J_URI | Yes | The URI of the Neo4j database (e.g., neo4j://127.0.0.1:7687) | |
| NEO4J_USER | Yes | The Neo4j database username | |
| NEO4J_PASSWORD | Yes | The Neo4j database password | |
| OPENAI_API_KEY | No | Optional OpenAI API key for enhanced entity extraction | |
| GRAPHITI_GROUP_ID | No | Optional namespace for organizing data | default |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_memoryC | Add an episode/memory to the knowledge graph. This is the primary way to add information. |
| search_memory_nodesC | Search for nodes (entities) in the knowledge graph |
| search_memory_factsC | Search for facts (relationships) in the knowledge graph |
| get_episodesC | Get recent episodes for a group |
| delete_episodeC | Delete an episode from the knowledge graph |
| delete_entity_edgeC | Delete an entity edge (fact) from the knowledge graph |
| get_entity_edgeB | Get an entity edge by UUID |
| clear_graphA | Clear all data from the knowledge graph (DESTRUCTIVE) |
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
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.