Control Audacity from MCP clients with Audacity-MCP

Audacity-MCP is a practical bridge for creators who already edit in Audacity and want an MCP-compatible assistant to help with repeatable audio work. The project packages a Python MCP server for Audacity via mod-script-pipe, so the useful angle is not another cloud audio editor; it is local control of an existing desktop editor from clients that can speak MCP.

Use it when you want to experiment with assistant-driven podcast cleanup, voiceover editing, transcription labels, export steps, or mastering prep while keeping the audio workflow anchored in Audacity. The PyPI package currently lists audacity-mcp as a beta Python package for AI-driven audio editing via mod-script-pipe and requires Python 3.10 or newer.

Evaluation notes before using it in production:

• Treat it as a beta tool and test on copied project files first.
• Audacity must support the scripting path the tool relies on; check Audacity's own scripting documentation before setup.
• Review the install scripts and dependencies before running them on a creator workstation.
• Do not assume the assistant's audio choices are final; keep human listening and export QA in the loop.

Good fit: podcasters, video editors, musicians, and automation builders who want to turn repeated Audacity actions into promptable local workflows without uploading raw audio to a hosted editor.