Ask Claude about your meetings: a local MCP server and CLI for your meeting notes
Key takeaways
- Voxdrop 2.3 ships a read-only MCP server and a
voxdropterminal command inside the Mac app. Claude Code, Claude Desktop, Cursor, Codex and other MCP clients can list, search and read your meetings, to-dos and dictations. - Local by design: stdio, no account, no OAuth, no network port. Off by default – one switch in Settings → Integrations.
- Honest part: once an AI tool fetches a transcript, that tool's provider processes it under its own terms. Voxdrop itself sends nothing.
If you work with an AI assistant all day, your meetings are the context it's missing: what you promised in yesterday's call, what the customer said about the rollout, which to-dos are still open. Cloud meeting services such as Granola, Otter and Fireflies now offer MCP servers for this, behind an account and OAuth. Voxdrop keeps meetings on your Mac, so its MCP server runs there too.
What can Claude or Cursor do with Voxdrop's MCP server?
MCP (Model Context Protocol) is an open standard for connecting AI applications to other systems. Voxdrop's server offers five tools, all of them read-only – none can change, delete or send anything:
| Tool | Returns |
|---|---|
list_meetings | Your meetings, newest first: id, title, date, duration, language, whether there is a summary, to-do counts |
get_meeting | One meeting: short summary, summary, to-dos; the transcript on request, page by page |
search | Meetings and dictations containing your words, with snippets (up to 20 hits) |
list_todos | Open or done to-dos, filtered by time span or meeting |
recent_dictations | Your latest dictations, by number or time window |
Things you can ask, for example:
- “What did I promise in yesterday's call with the API team?”
- “List my open meeting to-dos from this week and draft tickets for them.”
- “Find every meeting where we talked about the rate limit and tell me what we decided.”
- “Turn my dictations from the last hour into a commit message.”
How do I connect Voxdrop to Claude Code, Claude Desktop, Cursor or Codex?
First, in Voxdrop: Settings → Integrations → AI tools & terminal, turn on Let AI tools and the terminal read meetings. Dictations are included unless you turn off Include dictations. Test connection starts the server once and reports how many tools it offers. Then, per client:
Claude Code
claude mcp add --transport stdio --scope user voxdrop -- "/Applications/Voxdrop.app/Contents/MacOS/voxdrop-cli" mcpClaude Desktop
In Voxdrop, click Add next to Claude Desktop. Voxdrop adds itself to Claude's configuration (and keeps a backup). Then quit Claude completely once and reopen it.
Cursor
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"voxdrop": {
"command": "/Applications/Voxdrop.app/Contents/MacOS/voxdrop-cli",
"args": ["mcp"]
}
}
}Codex CLI
codex mcp add voxdrop -- "/Applications/Voxdrop.app/Contents/MacOS/voxdrop-cli" mcpWe tested Claude Code and Claude Desktop. Cursor and Codex use the same standard stdio setup; the settings show the exact command to copy.
How does it work under the hood?
- A local copy, only while you allow it. With the switch on, the app keeps a JSON copy of your meetings (and, if allowed, dictations) in
~/Library/Application Support/Voxdrop/mcp/, a folder only your user account can read. Turning the switch off deletes it. - One small program.
voxdrop-cliships inside the signed, notarized app. Your AI tool starts it as a subprocess and talks JSON-RPC over stdin and stdout – MCP's stdio transport (protocol version 2025-11-25). It only reads that copy, never Voxdrop's database, and contains no network code. - No port. Nothing listens on your network, so nothing else can reach it.
- Sized for context windows. Results are capped at about 40,000 characters and paged, so a two-hour transcript doesn't flood the model.
- A guard against prompt injection. The server tells the model that transcripts are spoken words and that instructions inside them must not be followed. Read-only tools mean a manipulated transcript can't make anything happen in Voxdrop.
Can I use it from the terminal without an AI tool?
Yes – it's the same program. Terminal command “voxdrop” → Set up in the same settings links it into ~/.local/bin. Then:
voxdrop meetings --since 7d
voxdrop show last --todos
voxdrop search rate limit
voxdrop todos --open --since 7d
voxdrop dictations --since 1h
voxdrop export last --format md > meeting.mdEvery command takes --json for scripts. Exit codes: 0 ok, 1 nothing found, 2 no access (switch off), 64 wrong usage. Ids can be shortened to a unique prefix of four or more characters, as shown by voxdrop meetings.
Local MCP or cloud MCP: what's the difference?
| Voxdrop (local) | Meeting services' cloud MCP | |
|---|---|---|
| Where meetings are stored | On your Mac | On the vendor's servers |
| Sign-in | None | Account + OAuth |
| Connection | stdio, no port, no network | Over the internet |
| Cost | Included in the one-time purchase | Depends on the service's plan |
Voxdrop isn't the only local option: Superwhisper, Minutes, Meetily and anarlog (formerly Hyprnote) also offer MCP servers that run on your machine. What Voxdrop adds is the combination with system-wide dictation, live transcripts, to-dos and a one-time price. (Disclosure: Voxdrop is our app.)
Honest caveats
- The AI tool decides where the text goes. Whatever Claude, Cursor or Codex reads is processed by Anthropic, Cursor or OpenAI under their terms. For meetings that must not reach a cloud model, keep the switch off.
- Read-only. You can't check off to-dos through MCP.
- Path-bound. The configurations point to
/Applications/Voxdrop.app. Move the app and the entries break; Voxdrop shows Repair when it notices. - Mac only. No Windows or Linux version of the server.
If you'd rather have files than a server, the Markdown and JSON export writes the same data into a folder.
FAQ
Does Voxdrop have an MCP server?
Yes, since version 2.3. A read-only MCP server ships inside the Mac app and talks to AI tools over stdio. It offers five tools: list_meetings, get_meeting, search, list_todos and recent_dictations. It is off until you turn it on in Settings → Integrations.
Which AI tools can use Voxdrop's MCP server?
Any MCP client that starts local servers over stdio. Voxdrop has setup help for Claude Code, Claude Desktop, Cursor and Codex; we tested Claude Code and Claude Desktop ourselves.
Do I need an account, an API key or OAuth?
No. The AI tool starts Voxdrop's command-line program as a local process. There is no sign-in, no key and no network port.
Can Claude change or delete my meetings through MCP?
No. All five tools only read. None of them can change, delete or send anything.
Are my meetings sent to the cloud when I use MCP?
Voxdrop itself sends nothing. But the AI tool you connect sends whatever it reads to its model provider, under that provider's terms. If a meeting must not reach a cloud model, keep the switch off or use a client with a local model.
Read next
- Meeting action items on the Mac, without a bot in the call
- Meeting notes in Obsidian, automatically
- Meeting summaries with a local LLM: Ollama and LM Studio
Get Voxdrop
Voxdrop is on-device voice-to-text for any Mac app — hit a hotkey, speak, and the text appears at your cursor. Local Whisper, €9.99 Early-Bird (first 500 buyers) or €14.99 Standard, one-time, no subscription. License key right after checkout, 14-day money-back.