🧠 AI Memory System powered by MongoDB Atlas & Voyage AI - Autonomous memory management with zero manual work
Memory MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. 🧠 AI Memory System powered by MongoDB Atlas & Voyage AI - Autonomous memory management with zero manual work.
Experience the power of semantic code search and persistent AI memory
The server ships on npm as memory-engineering-mcp, 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.
Once Memory is connected, these are the calls the assistant has available:
memory_engineering_init — Initialize projectmemory_engineering_memory — Read/Update memoriesmemory_engineering_search — Semantic searchmemory_engineering_sync — Sync code embeddingsmemory_engineering_system — Health & diagnosticsInstallation — The Installation tool exposed by this serverDebugging — The Debugging tool exposed by this serverYou will need 2 environment variables: MONGODB_URI, VOYAGE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
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. Memory's toolset — memory_engineering_init, memory_engineering_memory, memory_engineering_search and 4 more — is a fair guide to whether it matches your workflow. It is maintained by romiluz13; 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 |
|---|---|
| memory_engineering_init | Initialize project |
| memory_engineering_memory | Read/Update memories |
| memory_engineering_search | Semantic search |
| memory_engineering_sync | Sync code embeddings |
| memory_engineering_system | Health & diagnostics |
| Installation | The Installation tool exposed by this server. |
| Debugging | The Debugging tool exposed by this server. |
{
"mcpServers": {
"memory-engineering-mcp": {
"command": "npx",
"args": ["memory-engineering-mcp"],
"env": {
"MONGODB_URI": "your-mongodb-atlas-uri",
"VOYAGE_API_KEY": "your-voyage-api-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MONGODB_URI | Configuration value read at startup. | Optional |
| VOYAGE_API_KEY | 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.