Audacity-MCP

AudacityMCP

AI-powered audio editing in Audacity through the Model Context Protocol

•

•

•

•

AudacityMCP connects any MCP-compatible AI assistant to Audacity, giving it full control over audio editing through 144 tools spanning effects, cleanup, mastering, transcription, and more. Talk to your AI assistant and it edits your audio in real-time.

No cloud. No API keys for audio processing. Everything runs locally through Audacity's named pipe interface.

If this is useful to you, a star helps other people find it — that's the whole marketing budget for this project. Want to help keep it maintained? Click the Sponsor badge up top.

> Compatibility: AudacityMCP currently works with Audacity 3.x only. Audacity 4.x is not yet supported — we hope to add support in the future.

Works With

AudacityMCP works with any AI client that supports the Model Context Protocol:

• Claude Desktop — Anthropic's desktop app
• Claude Code — CLI agent
• Cursor — AI code editor with MCP support
• Any other MCP-compatible client

Quick Start

1. Get AudacityMCP

Option A: Click the green Code button above → Download ZIP → extract to a folder

Option B: Clone with git:

git clone https://github.com/xDarkzx/Audacity-MCP.git

2. Run the installer (sets up everything else automatically)

Windows: either double-click `install.bat` in File Explorer, or — if you're already in a terminal from the `git clone` step above — just keep going in the same PowerShell/Command Prompt window:

cd Audacity-MCP
.\install.bat

macOS / Linux:

cd Audacity-MCP
bash install.sh

> The installer does 3 things: installs `audacity-mcp` from this local folder (the one you just downloaded/cloned — no PyPI or GitHub fetch involved), enables mod-script-pipe in Audacity, and configures Claude Desktop — no manual JSON editing needed. It asks for confirmation before touching either config file, explains exactly what it's about to do first, and always backs up an existing file before changing it. Want to see everything it would do without changing anything? Add `--dry-run`: `.\install.bat --dry-run` / `bash install.sh --dry-run`.

>

> Note: `install.bat`/`install.sh` must be run from inside this folder — they only install the code sitting right next to them, they don't download anything themselves.

Other MCP clients (Cursor, Claude Code, etc.)

If you're not using Claude Desktop, install manually with `pip install audacity-mcp-server` and add to your client's MCP config:

{
  "mcpServers": {
    "audacity": {
      "command": "audacity-mcp"
    }
  }
}

Check your client's MCP documentation for the config file location.

> Client can't find/run `audacity-mcp`? GUI apps don't always see the same PATH a terminal does. Run `python -c "import sysconfig; print(sysconfig.get_path('scripts'))"` and use the full path it prints (plus `\audacity-mcp.exe` on Windows or `/audacity-mcp` on macOS/Linux) as `"command"` instead of the bare name.

Prefer not to run a script at all? Full manual setup

No `install.bat`/`install.sh`, nothing touching your system automatically — three steps, all done by hand:

1. Enable mod-script-pipe in Audacity: Edit → Preferences (Windows/Linux) or Audacity → Preferences (macOS) → Modules → set `mod-script-pipe` to Enabled → OK → restart Audacity.

2. Install the package: open a terminal (Command Prompt/PowerShell on Windows, Terminal on macOS/Linux) and run `pip install audacity-mcp-server` — a normal PyPI install, no repo clone needed.

3. Configure Claude Desktop: open Claude Desktop → Settings (gear icon) → Developer tab → Edit Config — this opens `claude_desktop_config.json` in a text editor. Add this inside the `"mcpServers"` block, keeping any other servers you already have:

{
     "mcpServers": {
       "audacity": {
         "command": "audacity-mcp"
       }
     }
   }

Save the file and fully restart Claude Desktop (quit from the system tray, not just close the window).

That's the entire install — see the Installation Guide for the same steps with more detail and per-OS notes.

> `"audacity"` doesn't show up as a tool after restarting? The `"command": "audacity-mcp"` above only works if that command is on the same PATH Claude Desktop itself uses, which isn't always the case (especially if Claude Desktop was already open when you installed Python). If it doesn't connect, run this in a terminal to find the real install location: `python -c "import sysconfig; print(sysconfig.get_path('scripts'))"` — then replace `"audacity-mcp"` above with the full path it prints plus `\audacity-mcp.exe` (Windows, remember to double every backslash: `\\`) or `/audacity-mcp` (macOS/Linux).

3. Start editing

Open Audacity, load some audio, then talk to your AI:

"Clean up this podcast recording"
"Master this track for Spotify, it's EDM"
"Transcribe this and add labels at each sentence"
"Add reverb with a large room, then export as FLAC"

> Audacity must be open first. AudacityMCP communicates through Audacity's named pipe — it can't launch Audacity for you.

> See the full Installation Guide for detailed setup on all platforms and MCP clients.

Why AudacityMCP?

Without AudacityMCP: You manually navigate menus, tweak effect parameters by ear, apply effects one at a time, look up ACX specs, and repeat until it sounds right.

With AudacityMCP: You describe what you want in plain English and the AI handles the rest — picking the right effects, setting industry-standard parameters, and chaining operations together.

AudacityMCP is especially useful for:

• Podcasters who want consistent, professional sound without audio engineering knowledge
• Musicians who need quick mastering with genre-appropriate settings
• Content creators working with interviews, voiceovers, or field recordings
• Anyone who'd rather describe what they want than click through menus

What Can It Do?

You:  "Clean up this podcast recording"
AI:   Runs auto_cleanup_podcast → HPF 80Hz → noise reduction → compression → safe loudness check

You:  "Master this track for Spotify, it's EDM"
AI:   Runs auto_master_music style=edm → HPF 30Hz → click removal → compression 2.5:1 → bass +2dB → loudness check

You:  "This is a noisy live recording, fix it up"
AI:   Runs auto_cleanup_live → HPF 100Hz → click removal → noise reduction 18dB → compression 5:1

You:  "Transcribe this interview and add labels"
AI:   Runs transcribe_to_labels → faster-whisper transcription → Audacity labels at each timestamp

You:  "Add reverb to the vocals, then export as FLAC"
AI:   select region → reverb effect → export to FLAC

Features

144 Tools Across 11 Categories

Pipelines

AudacityMCP includes 9 one-click pipelines for common audio tasks. Each pipeline is designed to be safe for badly recorded audio — it will never boost your audio dangerously. Pipelines clean up and improve your audio, then you can manually adjust loudness afterward if needed.

How Pipelines Work

1. You tell the AI what you want (e.g. "clean up this podcast")

2. The AI picks the right pipeline and starts it

3. The pipeline runs in the background — you get a `job_id` back

4. Poll with `check_pipeline_status` every 15-30 seconds to monitor progress

5. When done, a popup appears in Audacity

> Safety rule: Pipelines only reduce peaks if they're too hot. They never boost loudness. If you want to hit a specific LUFS target (e.g. -14 for Spotify), ask the AI to run `loudness_normalize` after you've checked the results look good.

Pipeline Reference

`auto_analyze_audio` — Analyze before processing

Measures your audio and recommends the best pipeline. Run this first if you're not sure what to do.

You: "Analyze this audio"
→ Returns: peak level, noise floor, clipping status, recommended pipeline

`auto_cleanup_audio` — Safe cleanup only

Cleans up noise and artifacts without changing loudness at all. Use when levels are already fine.

You: "Just clean up the noise, don't change the volume"
→ DC offset removal → HPF 80Hz → noise reduction → click removal (optional)

`auto_cleanup_podcast` — Podcast / voiceover

Professional broadcast processing for spoken word.

You: "Clean up this podcast recording"
→ DC offset → HPF 80Hz → noise reduction 12dB → compression 3:1 → safe loudness check

`auto_audiobook_mastering` — Audiobook (ACX/Audible)

Targets ACX requirements for audiobook distribution.

You: "Master this for ACX / Audible"
→ DC offset → HPF 80Hz → noise reduction 12dB → compression 2.5:1 → safe loudness check → peak cap -3dB

`auto_cleanup_interview` — Interview / dialogue

Light touch for conversations — preserves natural dynamics.

You: "Clean up this interview recording"
→ DC offset → HPF 80Hz → noise reduction 8dB → compression 2.5:1 → safe loudness check

`auto_cleanup_vocal` — Singing / studio vocal

Tuned for vocal recordings with presence EQ for clarity.

You: "Process this vocal recording"
→ DC offset → HPF 100Hz → noise reduction 10dB → compression 3:1 → presence EQ (+3dB treble, -1dB bass) → safe loudness check

`auto_cleanup_live` — Live / field / noisy recording

Aggressive cleanup for noisy environments. First 0.5s must be ambient noise for profiling.

You: "This is a noisy live recording, clean it up"
→ DC offset → HPF 100Hz → click removal → noise reduction 18dB → compression 5:1 → safe loudness check

`auto_master_music` — Music mastering

Genre-tuned mastering with 6 presets: `edm`, `hiphop`, `rock`, `pop`, `classical`, `acoustic`.

You: "Master this hip-hop track"
→ HPF 30Hz → click removal → compression 2:1 → bass +3dB treble +1dB → safe loudness check

You: "Master this for a classical album"
→ HPF 30Hz → click removal → compression 1.3:1 (very gentle) → no EQ → safe loudness check

`auto_lofi_effect` — Creative lo-fi / vintage

Apply a warm, vintage lo-fi sound. Presets: `light`, `medium`, `heavy`.

You: "Give this a lo-fi vibe"
→ HPF → LPF (muffled highs) → bass/treble warmth → compression 2:1 → safe loudness check

After a Pipeline: Adjusting Loudness

Pipelines intentionally leave loudness alone (they only reduce if peaks are clipping). To hit a streaming target:

You: "Now normalize this to -14 LUFS for Spotify"
→ AI uses loudness_normalize tool with lufs_level=-14

You: "Normalize to -16 LUFS for podcast"
→ AI uses loudness_normalize tool with lufs_level=-16

> Why not do this automatically? LUFS normalization can boost quiet/badly recorded audio by 10-20 dB, which blows it out. By separating cleanup from loudness, you get to check the results before the final loudness step.

Local Transcription (Experimental)

> This feature is experimental and requires separate setup. Everything else works without it.

Powered by faster-whisper — runs entirely offline, your audio never leaves your machine:

• 5 model sizes: `tiny`, `base`, `small`, `medium`, `large-v3`
• Transcribe full audio or just a selection
• Export as SRT, VTT, or plain text subtitles
• Auto-add Audacity labels at each spoken segment
• Language detection or specify 99+ languages

> Setup required before first use: See Transcription Setup for installation steps.

Want GPU acceleration (10-20x faster)? Run `audacity-mcp-setup-gpu` — or download `setup_gpu.bat`/`setup_gpu.sh` and double-click/run it if you'd rather not use a terminal. Detects your GPU, installs what's needed, and verifies it actually works. NVIDIA GPUs only (AMD/Intel graphics and macOS aren't supported by the transcription backend at all — any NVIDIA card works, GeForce isn't a requirement, just having an NVIDIA GPU is). No NVIDIA GPU? CPU works fine, just slower on long files.

>

> Script says it worked but transcription is still slow/on CPU? That means Claude Desktop is launching `audacity-mcp` from a different Python than the one the script just verified — see the fix (a manual config edit, five minutes).

What's New — v0.1.3

32 new tools (99 → 131), pipeline tuning fixes, and live-tested against Audacity.

• New effects: Reverse, Invert, Repair, AutoDuck, NotchFilter, VocalReduction, AdjustableFade, StudioFadeOut, CrossfadeClips, CrossfadeTracks, ClipFix, SlidingStretch, Tremolo
• New editing: Split (in place), SplitCut, SplitDelete, Disjoin + renamed old split → `edit_split_new`
• New tracks: StereoToMono, MixAndRenderToNew, MuteAll, UnmuteAll, Resample, AlignEndToEnd, AddLabelTrack
• New selection: CursorToTrackStart/End, CursorToProjectStart/End, SelectCursorToTrackEnd
• New project: EditMetadata, ImportMIDI
• New labels: RegularIntervalLabels
• Pipeline fixes: ACX peak cap -3.0→-3.5dB, live NR 18→12dB, podcast comp 10ms/1s→30ms/200ms, interview release 1s→200ms
• Bug fix: `effect_repair` now uses long timeout (Audacity shows popup on invalid selection)
• Validation: Added missing range checks on AutoDuck, VocalReduction, SlidingStretch, Resample

Troubleshooting

mod-script-pipe Not Enabled

The installer enables this automatically, but if it didn't work (e.g. Audacity was never opened before), enable it manually:

1. Open Audacity

2. Go to Edit → Preferences (Windows/Linux) or Audacity → Preferences (macOS)

3. Click Modules in the left sidebar

4. Set `mod-script-pipe` to Enabled

5. Click OK and restart Audacity

Connection Issues

Pipeline Issues

Audio Quality Tips

General Issues

Architecture

┌──────────────┐     stdio      ┌──────────────┐   named pipe   ┌──────────────┐
│  MCP Client  │◄──────────────►│ AudacityMCP  │◄──────────────►│   Audacity   │
│(AI assistant)│    (JSON-RPC)  │   FastMCP    │  (commands)    │              │
└──────────────┘                └──────────────┘                └──────────────┘
                                       │
                                       ├── audacity_mcp/main.py          (entry point)
                                       ├── audacity_mcp/audacity_client.py (pipe I/O)
                                       ├── audacity_mcp/tool_registry.py  (auto-loader)
                                       └── audacity_mcp/tools/            (11 modules)

Key Design Decisions

• Named pipes, not TCP — Direct IPC to Audacity's `mod-script-pipe`. No network exposure, no port conflicts.
• Zero `exec`/`eval` — Every operation maps to a static handler with input validation. No arbitrary code execution.
• Cross-platform — Windows uses Win32 API via ctypes, Unix uses standard file I/O.
• Async throughout — All tool handlers are `async`. Blocking pipe I/O runs in an executor pool with configurable timeouts.
• Safe pipelines — Pipelines measure audio before making loudness decisions. They only reduce, never boost.
• Dynamic tool registration — Drop a module in `audacity_mcp/tools/`, export a `register(mcp)` function, and it's automatically discovered.

Project Structure

AudacityMCP/
├── audacity_mcp/
│   ├── main.py                 # FastMCP server entry point
│   ├── audacity_client.py      # Cross-platform named pipe client
│   ├── tool_registry.py        # Auto-discovers and registers tool modules
│   └── tools/
│       ├── analysis_tools.py   # Audio analysis (contrast, spectrum, beats)
│       ├── cleanup_tools.py    # Noise reduction, mastering, 9 pipelines
│       ├── edit_tools.py       # Cut, copy, paste, split, join, trim
│       ├── effects_tools.py    # Reverb, echo, pitch, EQ, filters
│       ├── generate_tools.py   # Tone, noise, chirp, DTMF generation
│       ├── label_tools.py      # Label management
│       ├── project_tools.py    # Project/file operations
│       ├── selection_tools.py  # Selection and cursor control
│       ├── track_tools.py      # Track management
│       ├── transcription_tools.py  # Whisper-based transcription
│       └── transport_tools.py  # Playback and recording control
├── audacity_mcp_shared/
│   ├── constants.py            # Pipe paths, timeouts, allowed formats
│   ├── error_codes.py          # Typed error codes (pipe/command/validation)
│   └── pipe_protocol.py        # Command formatting and response parsing
├── tests/                      # 60 tests
├── docs/
│   ├── INSTALLATION.md         # Detailed setup guide
│   └── TOOLS.md                # Complete tool reference
└── pyproject.toml

Development

# Install dev dependencies
pip install -e ".[dev]"

# Run tests
pytest tests/ -x -q

# Run lint (real bugs + security patterns, not style/formatting)
ruff check .

Adding New Tools

1. Create a module in `audacity_mcp/tools/` (or add to an existing one)

2. Export a `register(mcp: FastMCP)` function

3. Define your tools with `@mcp.tool()` decorators

4. That's it — the tool registry auto-discovers it on startup

# audacity_mcp/tools/my_tools.py
from mcp.server.fastmcp import FastMCP
from audacity_mcp_shared.error_codes import AudacityMCPError, ErrorCode

def register(mcp: FastMCP):
    from audacity_mcp.main import client

    @mcp.tool()
    async def my_custom_effect(intensity: float = 0.5) -> dict:
        """Apply my custom effect to the selected audio."""
        if not 0 
  

---

## Support

If AudacityMCP has saved you time or helped with your audio projects, consider sponsoring:

  

Your support helps keep this project maintained and free for everyone.

---

## Documentation

- **[Installation Guide](docs/INSTALLATION.md)** — Detailed setup for Windows, macOS, Linux
- **[Tool Reference](docs/TOOLS.md)** — Complete reference for all 144 tools with parameters and ranges
- **[Transcript-Based Editing](PODCASTS.md)** — Workflow guide for podcasts, interviews, and lectures (label-driven editing)
- **[Contributing](CONTRIBUTING.md)** — How to add tools and contribute
- **[Changelog](CHANGELOG.md)** — Version history and release notes

## Acknowledgments

Thanks to the following for reported bugs, ideas, and feedback that improved this project:

- [@Harsha-Jay-S](https://github.com/Harsha-Jay-S) — diagnosed the `effect_change_pitch`/`effect_change_speed` bug ([#15](https://github.com/xDarkzx/Audacity-MCP/issues/15)) with measured proof against real Audacity, pinpointing the exact root cause.

## License

Apache License 2.0 — see [LICENSE](LICENSE) for details.

Built by [Daniel Hodgetts](https://github.com/xDarkzx) • [𝕏 @daehonz1](https://x.com/daehonz1)