Local-first graph memory for AI assistants with SQLite, semantic search, and MCP tools.
Connect Memory Engine MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Local-first graph memory for AI assistants with SQLite, semantic search, and MCP tools. The memory engine mcp mcp server is what makes that connection.
Local-first, graph-aware long-term memory for AI assistants.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Memory — The Memory 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.
Configuration is passed through the environment: MEMORY_DB_PATH, MEMORY_HOST, MEMORY_API_TOKEN. 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.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Memory Engine MCP's toolset — Memory — is a fair guide to whether it matches your workflow. It is maintained by SimoneB79; 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 |
|---|---|
| Memory | The Memory tool exposed by this server. |
{
"mcpServers": {
"memory-engine": {
"url": "http://localhost:8085/sse",
"transport": "sse"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MEMORY_DB_PATH | Filesystem location the server is allowed to use. | Optional |
| MEMORY_HOST | Endpoint or connection string the server talks to. | Optional |
| MEMORY_API_TOKEN | Credential the server authenticates with. | Yes |
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.