Audacity MCP Server

What is Audacity MCP Server?

This project implements an MCP (Model Context Protocol) server that connects to Audacity via its mod‑script‑pipe interface. Using named pipes, it sends commands to Audacity and receives responses, allowing control (e.g. starting/stopping recording or playback) through MCP endpoints. It can be launched with the uv tool and integrated with the Claude Desktop client.

How to use Audacity MCP Server?

Install dependencies with uv add "mcp[cli]" httpx, then run uv run audacity_mcp_pipe.py from the project directory. For Claude Desktop, update claude_desktop_config.json to point to the project with an absolute path to uv.

Key features of Audacity MCP Server

• Communicates with Audacity using the mod‑script‑pipe interface via named pipes.
• Provides MCP tool endpoints for status, recording start/stop, and play/pause.
• Uses the uv tool to run the MCP server.
• Can be configured to launch using the Claude Desktop client.
• Requires Audacity 3.x+, Python 3.13+, and enabled mod‑script‑pipe.

Use cases of Audacity MCP Server

• Automating audio recording and playback through AI assistants.
• Integrating Audacity control into MCP‑compatible clients like Claude Desktop.
• Starting and stopping recordings programmatically without manual GUI interaction.
• Retrieving Audacity status for monitoring in scripting workflows.

FAQ from Audacity MCP Server

How do I connect Audacity MCP Server to Audacity?

Enable mod‑script‑pipe in Audacity’s preferences under Scripting/Remote Control, then restart Audacity. The server will use the named pipes created by Audacity.

Which Python dependencies are required?

The project requires httpx and mcp[cli].

What MCP endpoints does the server expose?

It exposes get_status, start_recording, stop_recording, play, and pause endpoints.

How do I fix a "spawn uv ENOENT" error?

Use an absolute path to uv in the Claude Desktop config (claude_desktop_config.json).

Why do I get "Failed to connect to Audacity: [Errno 61] Connection refused"?

Audacity may have created pipe files with an appended number (e.g. /tmp/audacity_script_pipe.to.501). Update the pipe paths in audacity_mcp_pipe.py to match.