Local-first MCP server serving a project's business-domain knowledge to MCP-compatible agents.
Connect Domain to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Local-first MCP server serving a project's business-domain knowledge to MCP-compatible agents. The domain mcp server is what makes that connection.
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 server ships on npm as vitest, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Drift — Every entry stores SHA-256 hashes of the files it references. On PR open, the agent cross-references the PR's touched files against the knowledgeUpdating — The Updating tool exposed by this serverUninstalling — To remove domain-memory from a specific project: delete .domain-memory/, remove the block from the client instruction files, and drop theConfiguration is passed through the environment: DOMAIN_MEMORY_HTTP_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
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. Domain's toolset — Drift, Updating, Uninstalling — is a fair guide to whether it matches your workflow. It is maintained by mashware; 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 |
|---|---|
| Drift | Every entry stores SHA-256 hashes of the files it references. On PR open, the agent cross-references the PR's touched files against the knowledge store via check_drift and asks the developer to review any affected entrie |
| Updating | The Updating tool exposed by this server. |
| Uninstalling | To remove domain-memory from a specific project: delete .domain-memory/, remove the block from the client instruction files, and drop the domain-memory entry from .mcp.json / .cursor/mcp.json / .vscode/mcp.json / .gemini |
{
"mcpServers": {
"domain-memory": {
"command": "npx",
"args": ["-y", "@mashware/domain-memory-server"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DOMAIN_MEMORY_HTTP_TOKEN | Credential the server authenticates with. | Yes |
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.