Claude Desktop

You can connect Claude Desktop to your journal using the MCP (Model Context Protocol). Once connected, Claude can search your notes, read specific entries, check your todos, and capture new notes — all from the Claude chat interface.

What is MCP?

MCP is a standard protocol that lets Claude Desktop connect to local tools and services. journal ships a built-in MCP server (journal mcp) that exposes your journal to Claude.

The inference (the AI reasoning) happens in Claude's cloud. The retrieval (the semantic search over your notes) happens locally on your machine. Your notes are shared with Claude as search results — not uploaded in bulk.

Setup

Add journal to Claude Desktop's MCP config file. Find the config at:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this block (create the file if it doesn't exist):

{
  "mcpServers": {
    "journal": {
      "command": "/usr/local/bin/journal",
      "args": ["mcp", "--repo", "/Users/you/journal"]
    }
  }
}

Replace /usr/local/bin/journal with the actual path to your journal binary (find it with which journal), and /Users/you/journal with the path to your journal repository.

Use an absolute path for the command. Claude Desktop doesn't inherit your shell's PATH, so a relative path like journal won't work. Always use the full path.

Restart Claude Desktop, and the journal tools appear.

What Claude can do

Once connected, Claude has access to these tools:

ToolWhat it does
searchSemantic search over your notes
showRead the full content of a specific note
recentSee your most recent notes
decisionsFind notes marked @decision
threadsSee project activity and stale threads
meetingsList recent meeting transcripts
todosList open @todo items
doneComplete a todo
captureAdd a new note
statsJournal metrics: note volume, streaks, open todos, decisions, top tags
todayYour day at a glance: today's note path, open todos, and meetings
askAsk a question answered from your notes, with path:line citations
synthRun a synthesis job (weekly/daily/meetings/decisions/stale) and return the draft

Try asking:

  • "What did I work on this week?"
  • "What decisions did I make about the Acme project?"
  • "Add a note that we decided to go with Redis Cluster @decision"
  • "What are my open todos? Mark the pricing one as done."

Resources

In addition to tools, journal exposes read-only resources that Claude can pull directly:

Resource URIContents
journal://todayToday's daily note (raw Markdown)
journal://recentThe 50 most recent note chunks, newest first
journal://projects/{slug}/indexA project's _index.md — replace {slug} with the project name

Prompts

journal also provides pre-assembled prompts that Claude can run without hand-crafting the synthesis request. The server assembles context from your journal and returns it as a ready-to-run prompt — no cloud calls are made server-side:

PromptArgumentsWhat it does
weekly-reflectionGathers this week's notes and assembles a weekly reflection prompt
decisions-reviewproject (optional)Gathers @decision notes and assembles a review prompt
project-statusproject (required), since (optional, e.g. 2w)Gathers recent project notes and assembles a status prompt

Privacy

The MCP server runs locally on your machine. Claude Desktop sends tool calls (like "search for X") to the local server, and the server runs the search and returns results. Your note content travels from your machine to Anthropic's cloud as part of Claude's context — the same as pasting text into a chat window.

If you want a fully local setup (including local AI inference), see Local MCP Clients.

Troubleshooting

Tools don't appear after restart: Check that the JSON is valid and the path to the binary is correct and absolute.

"Connection failed": Make sure journal --help works in your terminal and the path in the config matches.

Ollama needs to be running: The search tools require Ollama for embedding queries. Start Ollama before asking Claude to search your notes.