MeMesh — Local memory for Claude Code and MCP coding agents. One SQLite file, zero cloud required.
MeMesh — Local memory for Claude Code and MCP coding agents. One SQLite file, zero cloud required. The claude code buddy mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 9 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
remember — Store knowledge with observations, relations, and tagsrecall — FTS5 + sqlite-vec search with multi-factor scoring (relevance, recency, frequency, confidence, recall impact) — no LLM in the hot pathforget — Soft-archive (never deletes) or remove specific observationsconsolidate — LLM-powered compression of verbose memoriesexport — Share memories as JSON between projects or team membersimport — Import memories with merge strategies (skip / overwrite / append)learn — Record structured lessons from mistakes (error, root cause, fix, prevention)user_patterns — Analyze your work patterns — schedule, tools, strengths, learning areasverify_agent_work — Persist a verification report for background-agent work; reality-checks claimed file changes against git diffYou will need 5 environment variables: MEMESH_AUTO_CAPTURE, MEMESH_DB_PATH, ANTHROPIC_API_KEY, OPENAI_API_KEY, OLLAMA_HOST. 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.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
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. Claude Code Buddy's toolset — remember, recall, forget and 6 more — is a fair guide to whether it matches your workflow. It is maintained by pcircle-ai; 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 |
|---|---|
| remember | Store knowledge with observations, relations, and tags |
| recall | FTS5 + sqlite-vec search with multi-factor scoring (relevance, recency, frequency, confidence, recall impact) — no LLM in the hot path |
| forget | Soft-archive (never deletes) or remove specific observations |
| consolidate | LLM-powered compression of verbose memories |
| export | Share memories as JSON between projects or team members |
| import | Import memories with merge strategies (skip / overwrite / append) |
| learn | Record structured lessons from mistakes (error, root cause, fix, prevention) |
| user_patterns | Analyze your work patterns — schedule, tools, strengths, learning areas |
| verify_agent_work | Persist a verification report for background-agent work; reality-checks claimed file changes against git diff |
{
"mcpServers": {
"claude-code-buddy": {
"command": "npx",
"args": ["-y", "@pcircle/memesh"],
"env": {
"MEMESH_AUTO_CAPTURE": "your-value",
"MEMESH_DB_PATH": "your-value",
"ANTHROPIC_API_KEY": "your-value",
"OPENAI_API_KEY": "your-value",
"OLLAMA_HOST": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| MEMESH_AUTO_CAPTURE | Configuration value read at startup. | Optional |
| MEMESH_DB_PATH | Filesystem location the server is allowed to use. | Optional |
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| OLLAMA_HOST | Endpoint or connection string the server talks to. | 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.