Use Dimmy's MCP server from Claude CLI (advanced)

dimmy-mcp is the same small binary the Claude Desktop wizard installs. It speaks the Model Context Protocol over stdio and reads your meetings straight from disk, so any MCP client can run it, including the claude command from Claude Code.

Step 1: locate the dimmy-mcp binary

Two reliable ways to get a path. Simplest: connect Claude Desktop once (the wizard copies the binary into a known folder). Or point at the copy inside the installed app.

Step 2: add it to Claude CLI

Use claude mcp add. The important detail: all flags come BEFORE the server name, and a -- separates the name from the command. Use --scope user so Dimmy is available in every project, not just the current folder.

bash
# macOS
claude mcp add --scope user dimmy -- /Applications/Dimmy.app/Contents/Resources/dimmy-mcp

# Windows (use the real, expanded path to dimmy-mcp.exe)
claude mcp add --scope user dimmy -- "C:\Users\<you>\AppData\Local\Dimmy\current\dimmy-mcp.exe"

Or edit the config by hand

Claude Code stores MCP servers in ~/.claude.json (user / local scope), not in a config.json. Project-scoped servers go in a .mcp.json file at the repo root. Add dimmy as a sibling under mcpServers; keep any servers already there.

json
{
  "mcpServers": {
    "dimmy": {
      "type": "stdio",
      "command": "/Applications/Dimmy.app/Contents/Resources/dimmy-mcp",
      "args": [],
      "env": {}
    }
  }
}

Step 3: verify it loaded

bash
claude mcp list
claude mcp get dimmy

dimmy should appear as connected. Inside a claude session you can also run /mcp to see live status. If it shows failed, run the binary directly to read the first stderr line: a missing Dimmy config dir is the usual cause.

Step 4: use it from the terminal

bash
claude

> List my last 5 Dimmy meetings.
> Read the transcript of meeting <id> and summarise the action items.
> Fetch the Dimmy recap template, write a recap for meeting <id>, and save it back.

The tools you get

Stack it with other MCP servers

MCP is composable: Claude CLI can talk to several servers in one session. Common pairings:

• Dimmy + Notion MCP → "Summarise my last meeting and create a Notion page in <database>." See Send recaps to Notion.
• Dimmy + Filesystem MCP → "Read meeting <id>, then save the recap to ~/Documents/recaps/<title>.md."
• Dimmy + GitHub MCP → "Open an issue in <repo> based on the action items in my last standup."

Troubleshooting

• claude mcp list shows failed: run the binary directly from a terminal; the first stderr line names the cause (missing config dir, no permission on the meeting folder, etc.).
• Tool calls return empty: you have no meetings yet. Record one to verify the wiring.
• Stale data: dimmy-mcp reads from disk on every call. If values look old, your meeting folder might be on a synced drive that hasn't refreshed yet.
• Audit log: every call lands in Dimmy's config dir as mcp.calls.log (macOS ~/Library/Application Support/dimmy/, Windows %APPDATA%\dimmy\). Check it to confirm a tool was invoked.