What is the MetaWhisp MCP server, and why would I want one?

The whole point: stop copying transcripts into chat windows. Once your dictations are queryable, the AI stops being a typewriter and starts being a research assistant that already knows everything you said out loud this month.

What do I need before I start?

• macOS 14 or later on Apple Silicon (M1, M2, M3, or M4)
• MetaWhisp installed and used at least once, so at least one transcript exists on disk
• Claude Desktop (latest version) or Cursor (latest version) installed
• Both apps fully quit and reopened at least once after install
• A few minutes — there is no code to write

Pro tip: Dictate a few short test clips before you start, so the MCP server has something real to return. If your baseline transcripts are noisy, Claude will faithfully echo noisy transcripts back at you. Fix the source, not the consumer.

How do I turn on MetaWhisp's MCP server?

Once it's running, you'll see a green status indicator and the exact localhost URL the server is bound to. Copy that URL — you need it for the next two steps.

How do I connect MetaWhisp to Claude Desktop?

Claude Desktop reads MCP server definitions from a JSON file. You can edit it by hand, or use the in-app menu.

1. Quit Claude Desktop completely (Cmd+Q — closing the window is not enough on macOS).
2. Open Claude Desktop → Settings → Developer → Edit Config. This opens ~/Library/Application Support/Claude/claude_desktop_config.json in your default editor.
3. Paste the snippet from MetaWhisp's MCP panel. It looks like this:

   {
     "mcpServers": {
       "metawhisp": {
         "url": "http://127.0.0.1:7891/mcp"
       }
     }
   }

   The exact port (7891 in this example) is whatever MetaWhisp shows in its MCP panel — the app picks an open port automatically, so yours may differ.
4. Save the file. Reopen Claude Desktop.
5. Click the tools icon (the hammer/wrench symbol) in a new chat. You should see MetaWhisp's tools listed — typically one to list recent transcripts, one to fetch a specific transcript by ID or date, and one to search by keyword or topic. The exact names and parameters are documented in MetaWhisp's MCP panel.

That's it. Claude can now ask MetaWhisp for your transcripts mid-conversation. Try it: open a chat, type "what did I dictate yesterday about the pricing page?" and watch the tool call appear. For the deeper spec, Anthropic's MCP documentation for Claude Desktop walks through the same config file with a few more advanced options (timeouts, env vars, per-server logging) that are worth knowing once you have more than one server.

How do I connect MetaWhisp to Cursor?

Cursor's MCP setup mirrors Claude Desktop, with two config locations: global (affects every project) and workspace (affects only one project). For most people, global is the right call.

1. Quit Cursor completely.
2. Open Cursor → Settings → MCP → Add new global MCP server. This creates ~/.cursor/mcp.json on your machine.
3. Paste the same JSON snippet — Cursor speaks the same MCP spec as Claude Desktop:

   {
     "mcpServers": {
       "metawhisp": {
         "url": "http://127.0.0.1:7891/mcp"
       }
     }
   }

4. Save. Restart Cursor.
5. Open any project. Switch to Agent mode (Cmd+I or click the agent toggle at the top of the chat panel). MetaWhisp's tools appear in the model's tool list.

What can I actually do once it's connected?

This is the part that turned me from "MCP is cool I guess" into "how did I ever live without this." A few real queries I run every week:

• Find quotes on a topic: "Pull every dictation from the last 30 days where I mentioned pricing" — Claude reads the relevant transcripts and returns the matching chunks with timestamps.
• Summarize a week: "What did I say out loud this week?" — Claude reads every transcript since Monday and gives a structured summary.
• Hand off to Cursor: "Pull the bug repro from my dictation yesterday and turn it into a failing test in this repo" — Cursor reads the transcript, writes the test, runs it.
• Cross-reference meeting notes: In Cursor agent mode, ask "compare what I told the design team on Tuesday to what I told the eng team on Thursday" — Cursor pulls both transcripts, diffs the asks.

If you already use MetaWhisp's processing modes (Structured, Correct, Rewrite), those transformed transcripts are what the MCP server exposes — not the raw Whisper output. So the text Claude sees is the cleaned-up version, not the original mess.

What about privacy?

Two practical notes. First, Claude Desktop and Cursor are cloud products — when you ask a question, your prompt and any transcript text the model pulls do go to Anthropic's or Cursor's servers. That's not MetaWhisp sending data; that's how the host app works. If you need fully offline use, look at running local models with Ollama, which has its own MCP client. Second, the MCP server respects MetaWhisp's existing privacy settings — if you've excluded certain folders from indexing or marked transcripts private, those stay excluded.

How do I troubleshoot if it doesn't connect?

Most MCP issues fall into three buckets. Walk through them in order.

1. The MCP server isn't running

In MetaWhisp, check Settings → MCP Server. Is the toggle on? Is the status indicator green? If it's red or yellow, the server failed to bind — usually because another process is holding the port. Change the port in MetaWhisp's settings, update the URL in Claude's or Cursor's config, restart both.

2. The host app can't reach the server

The two most common culprits: Claude Desktop or Cursor was launched before MetaWhisp's server started, or the URL in the config doesn't match what's shown in MetaWhisp's panel. The fix is to fully quit the host app (Cmd+Q — verify with ps aux | grep -i claude or Activity Monitor), confirm MetaWhisp's server is green, then reopen the host app. macOS does not always auto-reconnect to localhost services across app restarts.

3. The server is reachable but the tools don't appear

Check the host app's MCP logs. Claude Desktop → Settings → Developer, then look at the server logs pane. Cursor → Settings → MCP, click the server entry, look at the output panel. If the server is talking but the host doesn't list the tools, the MCP spec version likely mismatched. Both Claude Desktop and Cursor require recent MCP spec versions — make sure you're on the latest build of MetaWhisp and on the latest build of the host app.

Pro tip: When debugging, leave MetaWhisp's MCP panel open. The request log shows every tool call as it happens, with the parameters the host sent and the response MetaWhisp returned. It's the fastest way to see whether the problem is on the server side or the client side.

What's next once it's working?

If you already dictate a lot, the MCP server quietly becomes the most-used tool in your stack. A few extensions worth trying:

• Dictate your prompts to Claude Code instead of typing them — same flow, but the prompt goes straight to Claude Code's agent loop with MetaWhisp's MCP tools already loaded.
• Dictate into Obsidian on the same Mac, then have Cursor pull those notes via MetaWhisp's MCP when you're working in a repo.
• Compare setups in our Google Stitch MCP overview if you're running multiple MCP servers in parallel and want patterns for keeping them organized.

The bigger pattern here: voice as input, AI as processor, your local files as the substrate. Once the plumbing is in place, you stop thinking about which tool to use and start thinking about what you want to say.

FAQ

About the author

Andrew Dyuzhov is the solo founder of MetaWhisp. He's a marketer-turned-builder with ADHD who assembled MetaWhisp on top of open-source Whisper because typing was the bottleneck on everything he wanted to ship. He dictates in Russian and English daily and uses Cursor + Claude Code + MetaWhisp's MCP as his main writing surface. Find him on X.

Related reading

• How to dictate prompts to Claude Code on Mac
• Dictate to Obsidian on Mac, the offline-friendly way
• Google Stitch MCP: what it is and how it fits your dev stack
• MetaWhisp processing modes: Structured, Correct, Rewrite