# Use Dimmy's MCP server from Claude CLI (advanced). Dimmy Help. > Use Dimmy's MCP server from Claude CLI (advanced). Step-by-step help for Dimmy, the native voice dictation app for macOS, Windows, and Linux. Source: https://dimmy.app/help/integrations-mcp-claude-cli/ [← Back to Help center](https://dimmy.app/help/) Integrations # Use Dimmy's MCP server from Claude CLI (advanced) Dimmy's MCP bridge has a one-click setup for Claude Desktop. There's no built-in button for the terminal, but you can point the Claude CLI at the same binary by hand. Here's how. warning This is an advanced, manual recipe. Dimmy ships a one-click wizard for [Claude Desktop](https://dimmy.app/help/integrations-claude-desktop/) only. Using the binary from the terminal is unofficial: it works because dimmy-mcp is a plain stdio MCP server, but Dimmy doesn't manage this wiring for you and may move the binary between versions. 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. info Finish [the Claude CLI setup](https://dimmy.app/help/integrations-claude-cli/) first. This recipe assumes claude --version works and you're signed in. The MCP binary itself ships on Windows and macOS; there is no Linux build of dimmy-mcp. ## 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. | Source | macOS | Windows | | ------------------------------- | ----------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | | Inside the app | /Applications/Dimmy.app/Contents/Resources/dimmy-mcp | next to Dimmy.exe, e.g. C:\\Users\\\\AppData\\Local\\Dimmy\\current\\dimmy-mcp.exe | | After connecting Claude Desktop | \~/Library/Application Support/Claude/Claude Extensions/dimmy/dimmy-mcp | %LOCALAPPDATA%\\Packages\\Claude\_pzs8sxrjxfjjc\\LocalCache\\Roaming\\Claude\\Claude Extensions\\dimmy\\dimmy-mcp.exe | tip Verify the path before wiring it up: run the binary directly. It should start and wait on stdin (Ctrl+C to quit). If it prints an error about a missing config dir, launch Dimmy once first. ## 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\\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 and summarise the action items. > Fetch the Dimmy recap template, write a recap for meeting , and save it back.` ## The tools you get | Tool | What it does | Typical use | | ------------------------------ | ----------------------------------------------------------------------- | ---------------------------------------------- | | dimmy\_get\_recent\_meetings | List recent meetings (id, title, ts, duration). | "Show me my last 10 meetings." | | dimmy\_get\_meeting | Full transcript + metadata + existing recap. | "Read the transcript of ." | | dimmy\_get\_recap\_template | Dimmy's recap Markdown template. | Called automatically before producing a recap. | | dimmy\_save\_recap | Write recap.md back into the meeting folder. | "Save this recap." | | dimmy\_get\_recent\_dictations | Listed, but returns a "not exposed yet" message in the current version. | Not usable yet. | ## 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 ." See [Send recaps to Notion](https://dimmy.app/help/integrations-notion/). * Dimmy + Filesystem MCP → "Read meeting , then save the recap to \~/Documents/recaps/.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. info Desktop and CLI can both point at the binary at once. Each MCP client spawns its own copy; the binary is stateless and reads from disk, so there's no conflict. Was this helpful? ## In this category [ IntegrationsConnect Claude Desktop to Dimmy (MCP bridge)One-click wizard installs a small MCP server. Ask Claude Desktop about your meetings, dictations, and let it write recaps back into Dimmy.](https://dimmy.app/help/integrations-claude-desktop/) [ IntegrationsUse your Claude subscription via Claude CLI (no API key)If you already pay for Claude Pro, Team, or Max, route Dimmy's LLM rewrites and recaps through the local claude CLI. No API key, no per-token cost.](https://dimmy.app/help/integrations-claude-cli/) [ IntegrationsSend meeting recaps to NotionDimmy has a built-in Notion integration. Connect once with your own integration token, pick a destination page or database, then send any recap with one button (or auto-send every meeting).](https://dimmy.app/help/integrations-notion/) [ IntegrationsUse your ChatGPT subscription via Codex (no API key)If you already pay for ChatGPT Plus, Pro, Team, Business, or Enterprise, route Dimmy's LLM rewrites and recaps through the local codex CLI. No API key, no per-token cost.](https://dimmy.app/help/integrations-codex-cli/) [ IntegrationsSend audio from your phone with TelegramConnect Dimmy to your own Telegram account. Record audio on your phone with any app, share it to your Telegram Saved Messages, and Dimmy transcribes it and writes a recap on your computer. Windows and macOS.](https://dimmy.app/help/integrations-telegram/) Last updated: 2026-05-22 On this page 1. [01 Step 1: locate the dimmy-mcp binary](#step-1-locate-the-dimmy-mcp-binary) 2. [02 Step 2: add it to Claude CLI](#step-2-add-it-to-claude-cli) 3. [03 Or edit the config by hand](#or-edit-the-config-by-hand) 4. [04 Step 3: verify it loaded](#step-3-verify-it-loaded) 5. [05 Step 4: use it from the terminal](#step-4-use-it-from-the-terminal) 6. [06 The tools you get](#the-tools-you-get) 7. [07 Stack it with other MCP servers](#stack-it-with-other-mcp-servers) 8. [08 Troubleshooting](#troubleshooting)