Using Dori Vault Memory in Claude Code & Cursor via MCP

How to connect Dori's local vault memory to your developer IDE or coding CLI using the Model Context Protocol.

Dori doesn’t just work inside its own desktop app—it acts as a system-wide memory provider for external AI tools via the open Model Context Protocol (MCP).

With Dori’s MCP server, your coding assistants (Claude Code, Cursor, Windsurf, Roo Code) can search your business notes, meeting decisions, and product specs directly while writing code.

1. Connecting Dori MCP to Claude Code

Dori’s MCP server runs over Streamable HTTP on the local engine — there’s no separate CLI to install. Under Settings → Connections → Use Dori elsewhere the app generates a ready-to-paste snippet, or you can run this directly:

claude mcp add --transport http dori http://127.0.0.1:8002/mcp

Now inside Claude Code, you can ask:

“What were the key database performance constraints we agreed on in yesterday’s meeting?”

Claude Code will call Dori’s memory_search tool, pull the matching note or transcript excerpt from your local vault, and apply those constraints to your code without you copy-pasting notes.

2. Connecting Dori MCP to Cursor / Windsurf

Merge this into ~/.cursor/mcp.json (or the equivalent config for Windsurf/Roo Code) under "mcpServers":

{
  "mcpServers": {
    "dori": {
      "url": "http://127.0.0.1:8002/mcp"
    }
  }
}

By default the engine binds to loopback (127.0.0.1) and no token is required. If you’ve turned on engine host auth, add the bearer token shown on the Connections page as an Authorization header.

Available MCP Tools Exposed by Dori

Dori exposes a curated subset of its own actions to external MCP clients — not raw database or filesystem access. The most relevant for coding tools:

MCP Tool Name	Description
`memory_search`	Hybrid FTS5 + vector search across indexed vault content, returning ranked text chunks with source references.
`tasks_list`	Lists pending tasks from the vault.
`tasks_create_many`	Creates one or more tasks in the vault.
`vault_write_markdown`	Creates a Markdown file in the vault, with optional frontmatter.
`workflow_list`	Lists active workflows (system and custom), including the input schema each expects for `workflow_start`.
`workflow_start`	Starts a workflow manually and returns the execution ID.