
Macwhisper Mcp Server
io.github.docdyhrPublished by GitHub account docdyhrv1.2.1Updated Oct 24, 2026
MacWhisper transcription for Claude Desktop. Fully local, no cloud, audio stays on your Mac.
Overview
Local MCP server that lets Claude Desktop transcribe audio files on a Mac through MacWhisper's CLI, with no cloud calls.
- What you can do
- Transcribe an audio file from an allow-listed folder, with optional model, language, engine and history-persistence options
- List installed transcription models and the folders the server may read from
- Cancel a running transcription
- Watch a folder and auto-transcribe new audio files into a done folder, then collect the results
- When to use it
- Useful on macOS when you want Claude to turn local recordings, memos or meeting audio into transcripts, summaries or action items without uploading the audio anywhere. It suits people who already use MacWhisper, or who have whisper.cpp set up for a fully open-source path.
- Requirements
- macOS only, with MacWhisper installed and licensed and its command-line tool enabled (or the whisper.cpp binary plus GGML models for the alternative engine). Python 3.13 via pyenv or the Homebrew/pip package, Claude Desktop, and the MACWHISPER_ALLOWED_PATHS environment variable listing readable directories; MACWHISPER_CLI and MACWHISPER_LOG_PATH are optional.
Installation
In SourceWeft
- Open Macwhisper Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
macwhisper-mcp-server
Local MCP server that connects MacWhisper to Claude Desktop.
What it does: Drop an audio file on your Desktop, then ask Claude to transcribe it, summarise it, or pull out action items — in one step. MacWhisper does the transcription on your Mac; Claude does the thinking. Nothing leaves your machine. No cloud APIs. No data ever leaves your Mac.
[CI] [CodeQL] [PyPI version] [License: MIT]
[Claude Desktop transcribing an audio file]
Requirements
- macOS (MacWhisper is macOS-only)
- MacWhisper — installed and licensed
- MacWhisper CLI enabled: open MacWhisper → Settings → Advanced → Command-Line Tool → Install. This places
mwat/usr/local/bin/mw. - Python 3.13.x via pyenv
- Claude Desktop
Installing MacWhisper via Homebrew:
After installation, enable the CLI in MacWhisper Settings as above. When you later run brew upgrade --cask macwhisper, the CLI symlink updates automatically — no re-install needed.
Install
Option A — Homebrew (recommended)
This installs the macwhisper-mcp binary into your Homebrew prefix. Upgrade later with brew upgrade docdyhr/tap/macwhisper-mcp-server.
Option B — pip / source
Or from source:
Verify the MacWhisper CLI is reachable:
Configure Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json and add:
Restart Claude Desktop.
Note: Audio files must be saved to your Mac's filesystem (Desktop, Downloads, or another allow-listed folder) before asking Claude to transcribe them. Files uploaded directly to the Claude chat window live in Claude's container and are not accessible to the local MacWhisper CLI.
Verify it works
In Claude Desktop, ask:
Transcribe ~/Desktop/memo.m4a
You should see a transcribe_audio tool call appear, followed by the transcript.
Available tools
Supported audio formats: .m4a .mp3 .mp4 .mov .wav .aiff .flac
Configuration
All configuration is via environment variables. Pass them through the env dict in claude_desktop_config.json (for Claude Desktop) or set them in .env for local development.
Local development: copy .env.example to .env and adjust. With direnv, .envrc exports .env automatically. Without direnv: source .env.
Per-directory language defaults
If you regularly transcribe recordings in a specific language, map a subfolder to
it instead of passing language on every call:
Drop a file in ~/Desktop/DK/ and transcribe_audio passes --language da
automatically. An explicit language argument on the tool call always wins over
the directory default.
Alternative engine: whisper.cpp
transcribe_audio(..., engine="whisper-cpp") transcribes using a standalone
whisper.cpp binary instead of
MacWhisper — useful if you don't have a MacWhisper license, or want a fully
open-source local path. It does not touch MacWhisper in any way.
Setup:
Homebrew installs the whisper-cli binary only — no models. Download a GGML
model yourself (this server never downloads anything over the network) from
huggingface.co/ggerganov/whisper.cpp,
e.g. ggml-base.en.bin, into a directory of your choice, then point the server at it:
Then call the tool with the model's filename (not a MacWhisper engine:model-id
string):
Transcribe ~/Desktop/memo.wav using the whisper-cpp engine with model ggml-base.en.bin
Limitations (v1):
- Input formats:
.wav,.mp3,.flaconly — not.m4a/.mp4/.mov/.aiff. This is whisper.cpp's own native format support; convert other formats first (e.g. withffmpeg) or use the default MacWhisper engine, which handles all supported formats. persist=trueis not supported — whisper.cpp has no history mechanism.- Default language is English (
en) if neitherlanguagenor a directory default is set — unlike MacWhisper, which defers to the app's own language selection.
Development
Logs
Security
- All file paths are resolved (symlinks followed) and checked against the
MACWHISPER_ALLOWED_PATHSallow-list before anything reaches the CLI. subprocess.runis always called with an argv list — nevershell=True.- No network calls. Ever.
See PRD §7 for the full threat model.
Known limitations
- Uploaded files: Files dragged into the Claude chat window live in Claude's container and are not accessible to the local MacWhisper CLI. Save the file to your Desktop or Downloads folder (or another allow-listed directory), then ask Claude to transcribe it from there.
- Danish letter names: Whisper may phonetically approximate letter names (e.g. "Æ, Ø, Å" → "E, Y, U") when they are spoken in isolation. Letters inside words transcribe correctly. This is a Whisper engine limitation, not a bug in this wrapper. See PRD §12.
- Cold-start latency: First transcription after MacWhisper launches takes ~13s (model load). Subsequent calls are ~2s.
License
MIT — see LICENSE.
Source: README.md at commit 1232879
Tools
0Version history
2- v1.2.1LatestOct 15, 2026
- v1.0.1Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts