Domain Memory MCP server
io.github.mashware/domain-memory·v0.2.4·4 starsLocal-first MCP server serving a project's business-domain knowledge to MCP-compatible agents.
4 stars41 downloads/wk
Reviews
Write oneNobody has reviewed Domain Memory yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Domain Memory tools (7, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
check_driftGiven a list of file paths (typically the files a PR touches), return the knowledge entries that reference them. Use at PR time to flag potentially stale entries.
get_project_primerRe-read the project primer from `.domain-memory/primer.md`. The primer is auto-delivered as MCP instructions on connection; this tool refreshes the content after editing without reconnecting.
read_stagingRead all staged findings for a given branch, ordered chronologically.
resolve_topic_keyLook up an active entry by its canonical topic_key (feature slug, or "<featureSlug>/<aspectSlug>"). Use before save_knowledge(create) when you already know the exact slug — faster and more reliable than search_knowledge for dedup.
save_knowledgewrite actionCreate, update, archive or supersede a knowledge entry. Always call search_knowledge first. Conflicts block the write — resolve with the user before retrying.
search_knowledgeSearch the domain-memory knowledge store using semantic + keyword + path/symbol matchers. Returns ranked candidates. Call before writing to avoid duplicates.
stage_findingAppend a domain-knowledge finding to the per-branch staging. Findings survive session compaction and are consolidated later at /save-knowledge or PR time.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan73 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 107 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Domain Memory compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,255 servers
- Tools
- 7
- the typical server has 7
- Tools that change things
- 14%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 4
- more than 82% of 28,688 servers
- Downloads a week
- 41
- more than 33% of 12,191 servers with a package
What its tools let an agent do: 6 read · 1 create
Install Domain Memory in Claude Code, Cursor or VS Code
Runs npx -y @mashware/domain-memory-server on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add domain-memory -- npx -y @mashware/domain-memory-server
What the publisher says
From the Domain Memory repository's README, as published. We do not edit it. Read it on GitHub
Domain Memory
A local MCP server that accumulates the business-domain knowledge of a software project — flows, integrations, decisions, nuances — and makes it available to any MCP-compatible agent (Claude Code, Cursor, Copilot, Gemini, OpenCode).
The goal is to capture the why behind the code: the stuff a new developer would need six months from now to understand why a thing is built the way it is. The what is already in the code — domain-memory does not duplicate it.
Status: Functional. Local install, single developer, local SQLite.
What this is
Domain Memory is a living glossary of your project's business domain — the concepts, rules, entities, and the why behind decisions — that grows as you build. The frame that matters: this is semantic memory (what "a German invoice" or "a deactivated account" means in your project, and why it behaves the way it does), not episodic memory (what you changed last Tuesday and in which commit). The episodic record already lives in git history; Domain Memory holds the part no diff captures.
You don't stop to write documentation. As the agent works it records findings on its own, and they are folded into the glossary when you run /save-knowledge or open a pull request — so the knowledge accrues from real work instead of becoming a separate authoring chore you have to remember.
Everything is plain markdown you own and version in git. Each entry is a human-readable file under .domain-memory/; the search index is derived from those files and can be rebuilt from them at any time, so the knowledge stays portable, reviewable in a pull request, and never locked inside a database.
If what you want is a history of work sessions, cross-machine sync, or generic per-user assistant memory, this is deliberately not that. Domain Memory stays narrow on purpose: the domain knowledge of one project, and nothing else.
How is this different from…
Domain Memory occupies a narrow niche. The closest neighbours and where it differs:
If you're asking "where does the agent remember that I prefer dark mode?", you want mem0. If you're asking "where does the agent remember that we deliberately bypass tax validation for German invoices because of the 2024 ruling?", you want this.
How it works
Three principles run the whole system:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Domain Memory: common questions
- Is Domain Memory MCP server safe?
- Mostly: it is graded B (82/100). Read the Domain Memory safety report
- How do I install Domain Memory?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Domain Memory need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Domain Memory maintained?
- The last commit was 145 days ago (2026-06-12). The latest release is v0.2.4.
- What can I use instead of Domain Memory?
- Servers from other publishers that do the same job: Memorix MCP server, Codebase Memory MCP server and Neo4j Memory MCP server.
- How does Domain Memory compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 14% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Domain Memory
Same job from other publishers: the closest match first, then the best rated.
MemorixLocal-first project memory with legacy MCP and 2026 discovery compatibility.not reviewedEstablishedB- Codebase MemoryCodebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.not reviewedWidely usedC
- Neo4j MemoryMCP Neo4j Knowledge Graph Memory Servernot reviewedEstablishedA
- Nautilus Compass MemoryLocal-first long-term memory for AI agents, with byte-recomputable signed verification receipts.not reviewedEstablishedB
- Domain LivenessIs this business's website still there? Checks apex and www, and DNS separately from HTTP.not reviewedEstablishedA
