mcpField
M
macwhisper-mcp-server

macwhisper-mcp-server

Local
github.com/docdyhrMedia & Design3Updated 3d ago

About macwhisper-mcp-server

macwhisper-mcp-server connects Claude Desktop to MacWhisper for local audio transcription on macOS. It can also use whisper.cpp, with path allowlists controlling file access.

Key features

  1. 01Transcribe audio locally
  2. 02MacWhisper and whisper.cpp engines
  3. 03List models and cancel jobs
  4. 04Watch folders for new audio
  5. 05Restrict access to allowed paths

Use cases

  1. 01Transcribe a recording for Claude Desktop
  2. 02Summarize or extract actions from a transcript
  3. 03Automatically transcribe new files in a watched folder

MCP support

The MCP server exposes tools to transcribe audio, inspect models and allowed paths, cancel transcription, and manage folder watching. Claude Desktop can call these tools on files accessible to the Mac.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"docdyhr-macwhisper": {
"command": "uvx",
"args": [
"macwhisper-mcp-server"
],
"env": {
"MACWHISPER_ALLOWED_PATHS": "<MACWHISPER_ALLOWED_PATHS>",
"MACWHISPER_CLI": "<MACWHISPER_CLI>",
"MACWHISPER_LOG_PATH": "<MACWHISPER_LOG_PATH>"
}
}
}
}
Run commanduvx macwhisper-mcp-server
Environment variables to set
MACWHISPER_ALLOWED_PATHSColon-separated list of directories the server may read audio files from (e.g. ~/Desktop:~/Downloads)
MACWHISPER_CLIPath to the mw binary. Auto-detected from /Applications/MacWhisper.app if omitted.
MACWHISPER_LOG_PATHLog file path. Defaults to ~/Library/Logs/macwhisper-mcp.log

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypimacwhisper-mcp-server1.2.1

Tools

6

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
pathstringYesAbsolute path to an audio file inside the configured allow-list. Supported formats: m4a, mp3, mp4, mov, wav, aiff, flac.
modelanyNoOptional model override in MacWhisper engine:model-id format, e.g. "whisperkit:openai_whisper-large-v3-v20240930" or "parakeet-pro:nvidia_parakeet-v3_494MB". Defaults to the model currently selected in MacWhisper.

Details

From the project 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.

Audio file  →  MacWhisper CLI  →  MCP server  →  Claude Desktop

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 mw at /usr/local/bin/mw.
  • Python 3.13.x via pyenv
  • Claude Desktop

Installing MacWhisper via Homebrew:

brew install --cask macwhisper

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)
brew tap docdyhr/tap
brew install docdyhr/tap/macwhisper-mcp-server

This installs the macwhisper-mcp binary into your Homebrew prefix. Upgrade later with brew upgrade docdyhr/tap/macwhisper-mcp-server.

Option B — pip / source
pip install macwhisper-mcp-server

Or from source:

git clone https://github.com/docdyhr/macwhisper-mcp-server.git
cd macwhisper-mcp-server

pyenv install 3.13.13   # skip if already installed
pyenv local 3.13.13
python -m venv .venv
source .venv/bin/activate
pip install -e .

Verify the MacWhisper CLI is reachable:

mw version

Configure Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json and add:

{
  "mcpServers": {
    "macwhisper": {
      "command": "macwhisper-mcp",
      "args": [],
      "env": {
        "MACWHISPER_ALLOWED_PATHS": "~/Desktop:~/Downloads",
        "FASTMCP_CHECK_FOR_UPDATES": "off"
      }
    }
  }
}

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

ToolDescription
transcribe_audio(path, model?, language?, persist?, engine?)Transcribe an audio file and return the transcript as plain text. language is an ISO 639-1 code (e.g. da) or auto; overrides any per-directory default. persist=true saves to MacWhisper history (MacWhisper engine only). engine is "macwhisper" (default) or "whisper-cpp" — see Alternative engine below.
list_models()List transcription models installed in MacWhisper, plus whisper-cpp models if MACWHISPER_WHISPERCPP_MODEL_DIR is configured; active MacWhisper model is marked
cancel_transcription()Cancel the currently running transcription
list_allowed_paths()Return the directories the server is allowed to read from
start_watch(folder)Watch a folder and auto-transcribe new audio files into ../done/
stop_watch()Stop the active folder watcher
get_watch_results()Return completed watch-folder transcriptions and clear the queue

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.

Env varDefaultDescription
MACWHISPER_ALLOWED_PATHS~/DesktopColon-separated list of directories the server may read from
MACWHISPER_CLIauto-detectedPath to the mw binary. Defaults to /Applications/MacWhisper.app/Contents/MacOS/mw if that file exists, otherwise mw on PATH
MACWHISPER_LOG_PATH~/Library/Logs/macwhisper-mcp.logLog file path (never stdout — that's reserved for MCP)
MACWHISPER_LANGUAGE_DEFAULTSnoneColon-separated dir=lang pairs (ISO 639-1, or auto) — files in a matching directory get --language automatically. Most specific directory wins; an explicit language argument always overrides.
MACWHISPER_WHISPERCPP_BINARYwhisper-cli on PATHPath to the whisper-cli binary, if not on PATH. Only used when engine="whisper-cpp".
MACWHISPER_WHISPERCPP_MODEL_DIRnoneDirectory containing your GGML .bin model files. Required to use engine="whisper-cpp" at all — see below.

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:

"MACWHISPER_LANGUAGE_DEFAULTS": "~/Desktop/DK=da:~/Desktop/DE=de"

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:

brew install whisper-cpp

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:

"MACWHISPER_WHISPERCPP_MODEL_DIR": "~/whisper-models"

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, .flac only — not .m4a/.mp4/.mov/.aiff. This is whisper.cpp's own native format support; convert other formats first (e.g. with ffmpeg) or use the default MacWhisper engine, which handles all supported formats.
  • persist=true is not supported — whisper.cpp has no history mechanism.
  • Default language is English (en) if neither language nor a directory default is set — unlike MacWhisper, which defers to the app's own language selection.

Development

source .venv/bin/activate
pip install -e ".[dev]"

# Tests
pytest -q

# Lint + format
ruff check .
ruff format .

# Pre-commit hooks (one-time setup)
pip install pre-commit
pre-commit install

# Smoke-test against a real audio file (server must not be running in Claude Desktop)
python scripts/smoke_test.py ~/Downloads/Test.m4a
Logs
tail -f ~/Library/Logs/macwhisper-mcp.log

Security

  • All file paths are resolved (symlinks followed) and checked against the MACWHISPER_ALLOWED_PATHS allow-list before anything reaches the CLI.
  • subprocess.run is always called with an argv list — never shell=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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.