MCP server for enabling memory for Claude through a knowledge graph
Most knowledge and memory work still happens through a UI a human drives. Fuzzy Memory MCP MCP server moves it into the conversation instead. MCP server for enabling memory for Claude through a knowledge graph.
A basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats. This version has been enhanced with fuse.js to provide fuzzy, semantic searching capabilities.
with on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 14 tools. What each one is for:
create_entities — Create multiple new entities in the knowledge graphInput — entities (array of objects)create_relations — Create multiple new relations between entitiesadd_observations — Add new observations to existing entitiesdelete_entities — Remove entities and their relationsdelete_observations — Remove specific observations from entitiesdelete_relations — Remove specific relations from the graphread_graph — Read the entire knowledge graphsearch_nodes — Performs a fuzzy semantic search for nodes in the knowledge graph using Fuse.jsentity — The matched entity objectscore — Confidence score from 0.0 to 1.0 (higher is better)Threshold — 0.6 (0.0 = perfect match, 1.0 = matches anything)Configuration is passed through the environment: MEMORY_FILE_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Fuzzy Memory MCP's toolset — create_entities, Input, create_relations and 11 more — is a fair guide to whether it matches your workflow. It is maintained by flrngel; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| create_entities | Create multiple new entities in the knowledge graph |
| Input | entities (array of objects) |
| create_relations | Create multiple new relations between entities |
| add_observations | Add new observations to existing entities |
| delete_entities | Remove entities and their relations |
| delete_observations | Remove specific observations from entities |
| delete_relations | Remove specific relations from the graph |
| read_graph | Read the entire knowledge graph |
| search_nodes | Performs a fuzzy semantic search for nodes in the knowledge graph using Fuse.js |
| entity | The matched entity object |
| score | Confidence score from 0.0 to 1.0 (higher is better) |
| Threshold | 0.6 (0.0 = perfect match, 1.0 = matches anything) |
| Location | independent matching |
| open_nodes | Retrieve specific nodes by name |
{
"mcpServers": {
"memory": {
"command": "npx",
"args": [
"-y",
"github:flrngel/fuzzy-memory-mcp#main"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MEMORY_FILE_PATH | Filesystem location the server is allowed to use. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.