Persistent memory for Claude Code — offline, single-file, hybrid search.
Melchizedek MCP server exists for a simple reason — assistants are far more useful when they can act on Melchizedek directly instead of describing what you should do. Persistent memory for Claude Code — offline, single-file, hybrid search.
Claude Code forgets everything between sessions - and knows nothing about your other projects. Melchizedek fixes both.
Once Melchizedek is connected, these are the calls the assistant has available:
Inspirations — This project stands on the shoulders of others. Key ideas borrowed from:You will need one environment variable: M9K_DB_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
melchizedek-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
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. Melchizedek's toolset — Inspirations — is a fair guide to whether it matches your workflow. It is maintained by louis49; 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 |
|---|---|
| Inspirations | This project stands on the shoulders of others. Key ideas borrowed from: |
{
"mcpServers": {
"melchizedek": {
"command": "npx",
"args": ["-y", "melchizedek-server"],
"env": {
"M9K_DB_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| M9K_DB_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.