This project adds new features to the Memory server offered by the MCP team. It allows for the creation and management of a knowledge graph that
This project adds new features to the Memory server offered by the MCP team. It allows for the creation and management of a knowledge graph that captures interactions via a language model (LLM). The mcp memory custom mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
Prerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverConfiguration — Before running the server, you can set the MEMORY_FILE_PATH environment variable to specify the path for the memory file. If not set, the server willInstallation goes through your MCP client rather than a global install: point it at @smithery/cli 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.
You will need one environment variable: MEMORY_FILE_PATH. 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. MCP Memory Custom's toolset — Prerequisites, Installation, Configuration — is a fair guide to whether it matches your workflow. It is maintained by BRO3886; 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 |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
| Configuration | Before running the server, you can set the MEMORY_FILE_PATH environment variable to specify the path for the memory file. If not set, the server will default to using memory.json in the same directory as the script. |
{
"mcpServers": {
"memory": {
"command": "node",
"args": ["/path/to/mcp-memory-custom/dist/index.js"]
}
}
}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.