Wisdomgraph runs on your own machine — the client starts it, so there is no endpoint to ping. 27 installs a week from npm. Last commit 12 Jul 2026.
Neo4j-native DIKW memory for Claude Code — knowledge that compounds across sessions
We read the source, 6 d ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
return subprocess.run(cmd, capture_output=True, text=True)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Today is the operative word: we check Wisdomgraph every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add wisdomgraph -e 'WISDOM_NEO4J_PASSWORD=<WISDOM_NEO4J_PASSWORD>' -- npx -y wisdomgraph
{
"mcpServers": {
"wisdomgraph": {
"command": "npx",
"args": [
"-y",
"wisdomgraph"
],
"env": {
"WISDOM_NEO4J_PASSWORD": "<WISDOM_NEO4J_PASSWORD>"
}
}
}
}
[mcp_servers.wisdomgraph]
command = "npx"
args = ["-y", "wisdomgraph"]
env = { WISDOM_NEO4J_PASSWORD = "<WISDOM_NEO4J_PASSWORD>" }
{
"mcpServers": {
"wisdomgraph": {
"command": "npx",
"args": [
"-y",
"wisdomgraph"
],
"env": {
"WISDOM_NEO4J_PASSWORD": "<WISDOM_NEO4J_PASSWORD>"
}
}
}
}
{
"servers": {
"wisdomgraph": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"wisdomgraph"
],
"env": {
"WISDOM_NEO4J_PASSWORD": "<WISDOM_NEO4J_PASSWORD>"
}
}
}
}
Put your own value in place of
<WISDOM_NEO4J_PASSWORD> (Neo4j password for wisdomGraph. Set via `wisdom connect` or export directly).
The author’s registry entry marks it as required.
Shared memory across devices, sessions, and agents for OpenClaw, Claude Code, and Codex.
Pull Deep Memory from across your Claude Code Sessions — when you need it.
Cross-vendor semantic memory: recall across Claude Code / Codex / Grok sessions by meaning.
Read-only visualization for Cortex memory, knowledge, sessions, traces, and codebase graphs.
Cross-session memory for Claude Code — context capture, semantic search, recall
Offline codebase knowledge graph: 91% token reduction vs naive RAG, plus cross-session agent memory.
Local memory for Claude Code. Semantic recall across session history with zero API calls.
Local-first memory for Claude Code and any MCP client: hybrid search + knowledge graph, $0/token.
Answers built from our own checks of this server.