← Docs

MCP server

docs.mcp.intro

Start the server

Wire it into Claude Desktop

Add this to

(macOS) or the equivalent on your platform:

Restart Claude. The ten tools below should appear in the MCP picker.

The ten tools

  • mddock_search— Hybrid recall (BM25 + vector) over the local vault
  • mddock_read— Read a doc by path or md:// URI
  • mddock_write— Create or update a doc (proposal-gated by default)
  • mddock_install— Fork a published project into the workspace
  • mddock_publish— Publish current project to the marketplace
  • mddock_resolve— Resolve md:// to current bytes + sha256
  • mddock_skill_register— Register a skill endpoint with this workspace
  • mddock_resolve_conflict— Apply a three-way merge for conflicting docs
  • mddock_dream_run— Run a dream cycle (extract / compact / suggest / prune)
  • mddock_audit— Verify the hash chain for the current vault

Read-only by default

Mutating tools (mddock_write, mddock_publish, mddock_resolve_conflict) write to a proposal store rather than touching the vault directly. You review proposals in the desktop client before they land — so an agent can't silently rewrite your notes.

Cursor / Continue / others

Any MCP-compliant client works. The transport is plain stdio JSON-RPC; no MDDock-specific glue required. See /docs/agent-protocol for the read-only HTTP surface (no MCP needed).

Troubleshooting

  • •mddock doctor — checks workspace, schema, and binary versions
  • •Logs land at ~/.mddock/logs/mcp.log
  • •If a tool is missing in the client, try mddock mcp --json from a terminal to confirm it boots