MCP server enabling persistent memory for AI models through a local knowledge graph
MCP server enabling persistent memory for AI models through a local knowledge graph. The mcp knowledge graph mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.
Store and retrieve information across conversations using entities, relations, and observations. Works with Claude Code/Desktop and any MCP-compatible AI platform.
Everything the assistant can do here goes through one of these:
aim_memory_store — Store new memories (people, projects, concepts)aim_memory_add_facts — Add facts to existing memoriesaim_memory_link — Link two memories togetheraim_memory_search — Search memories by keywordaim_memory_get — Retrieve specific memories by exact nameaim_memory_read_all — Read all memories in a databaseaim_memory_list_stores — List available databasesaim_memory_forget — Forget memoriesaim_memory_remove_facts — Remove specific facts from a memoryaim_memory_unlink — Remove links between memoriesParameters — The Parameters tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Knowledge Graph's toolset — aim_memory_store, aim_memory_add_facts, aim_memory_link and 8 more — is a fair guide to whether it matches your workflow. It is maintained by shaneholloman; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| aim_memory_store | Store new memories (people, projects, concepts) |
| aim_memory_add_facts | Add facts to existing memories |
| aim_memory_link | Link two memories together |
| aim_memory_search | Search memories by keyword |
| aim_memory_get | Retrieve specific memories by exact name |
| aim_memory_read_all | Read all memories in a database |
| aim_memory_list_stores | List available databases |
| aim_memory_forget | Forget memories |
| aim_memory_remove_facts | Remove specific facts from a memory |
| aim_memory_unlink | Remove links between memories |
| Parameters | The Parameters tool exposed by this server. |
{
"mcpServers": {
"Aim-Memory-Bank": {
"command": "npx",
"args": [
"-y",
"mcp-knowledge-graph",
"--memory-path",
"/Users/yourusername/.aim"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
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.