<strong>Website</strong> · Quickstart · MCP Tools · Pro · Changelog
Website · Quickstart · MCP Tools · Pro · Changelog. The neural memory mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 5 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
nmem_remember — Store a memory — auto-detects type, tags, and connectionsnmem_recall — Recall through spreading activation — related memories surface naturallynmem_health — Brain health score (A–F) with actionable fix suggestionsCommunity — The Community tool exposed by this serverEcosystem — The Ecosystem tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at neuralmemory on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
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. Neural Memory's toolset — nmem_remember, nmem_recall, nmem_health and 2 more — is a fair guide to whether it matches your workflow. It is maintained by nhadaututtheky; 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 |
|---|---|
| nmem_remember | Store a memory — auto-detects type, tags, and connections |
| nmem_recall | Recall through spreading activation — related memories surface naturally |
| nmem_health | Brain health score (A–F) with actionable fix suggestions |
| Community | The Community tool exposed by this server. |
| Ecosystem | The Ecosystem tool exposed by this server. |
Add to your editor's MCP config:
```json
{
"mcpServers": {
"neural-memory": { "command": "nmem-mcp" }
}
}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.