Memento MCP: Knowledge graph memory system for LLMs
Memento MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Memento MCP directly instead of describing what you should do. Memento MCP: Knowledge graph memory system for LLMs.
Scalable, high performance knowledge graph memory system with semantic retrieval, contextual recall, and temporal awareness. Provides any LLM client that supports the model context protocol (e.g., Claude Desktop, Cursor, Github Copilot) with resilient, adaptive, and persistent long-term ontological memory.
Once Memento MCP is connected, these are the calls the assistant has available:
diagnose_vector_search — Information about the Neo4j vector index, embedding counts, and search functionalityforce_generate_embedding — Forces the generation of an embedding for a specific entitydebug_embedding_config — Information about the current embedding service configurationEntities — Entities are the primary nodes in the knowledge graph. Each entity has:Relations — Relations define directed connections between entities with enhanced properties:Prerequisites — The Prerequisites tool exposed by this serverConfiguration — The Configuration tool exposed by this serverThe server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 8 environment variables: MEMORY_STORAGE_TYPE, NEO4J_URI, NEO4J_USERNAME, NEO4J_PASSWORD, NEO4J_DATABASE, NEO4J_VECTOR_INDEX, NEO4J_VECTOR_DIMENSIONS, NEO4J_SIMILARITY_FUNCTION. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Memento MCP's toolset — diagnose_vector_search, force_generate_embedding, debug_embedding_config and 4 more — is a fair guide to whether it matches your workflow. It is maintained by gannonh; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Memento MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| diagnose_vector_search | Information about the Neo4j vector index, embedding counts, and search functionality |
| force_generate_embedding | Forces the generation of an embedding for a specific entity |
| debug_embedding_config | Information about the current embedding service configuration |
| Entities | Entities are the primary nodes in the knowledge graph. Each entity has: |
| Relations | Relations define directed connections between entities with enhanced properties: |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Configuration | The Configuration tool exposed by this server. |
{
"mcpServers": {
"memento": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"MEMORY_STORAGE_TYPE": "your-value",
"NEO4J_URI": "your-value",
"NEO4J_USERNAME": "your-value",
"NEO4J_PASSWORD": "your-value",
"NEO4J_DATABASE": "your-value",
"NEO4J_VECTOR_INDEX": "your-value",
"NEO4J_VECTOR_DIMENSIONS": "your-value",
"NEO4J_SIMILARITY_FUNCTION": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| MEMORY_STORAGE_TYPE | Configuration value read at startup. | Optional |
| NEO4J_URI | Configuration value read at startup. | Optional |
| NEO4J_USERNAME | Configuration value read at startup. | Optional |
| NEO4J_PASSWORD | Configuration value read at startup. | Optional |
| NEO4J_DATABASE | Configuration value read at startup. | Optional |
| NEO4J_VECTOR_INDEX | Configuration value read at startup. | Optional |
| NEO4J_VECTOR_DIMENSIONS | Configuration value read at startup. | Optional |
| NEO4J_SIMILARITY_FUNCTION | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.