Skip to content
Dori Help Center
Esc
navigateopen⌘Jpreview
On this page

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.

Developer IDE / CLIClaude Code, Cursor,Windsurf, Roo CodeDori MCP Memory Serversearch_vault, read_projectget_meeting_decisionsDori Local VaultMarkdown Files &SQLite Domain DB

1. Connecting Dori MCP to Claude Code

Add Dori’s MCP server configuration to your ~/.claude.json or project .mcp.json:

{
  "mcpServers": {
    "dori-memory": {
      "command": "dori",
      "args": ["mcp", "serve"]
    }
  }
}

Now inside Claude Code, you can ask:

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

Claude Code will query Dori’s MCP memory server, pull the exact meeting transcript snippet from your local vault, and apply those constraints to your code without you copy-pasting notes!


2. Connecting Dori MCP to Cursor / Windsurf

In Cursor settings (Features → MCP Servers):

  1. Name: dori-memory
  2. Type: command
  3. Command: dori mcp serve

Available MCP Tools Exposed by Dori

MCP Tool Name Description
search_vault Runs hybrid FTS5 BM25 + vector search across all Markdown vault notes.
get_meeting_decisions Returns tracked commitments and decisions for a given person or project.
read_project_context Fetches active project specs, background briefs, and linked documents.
query_domain_records Queries local SQLite domain records for structured entity summaries.

Was this page helpful?