MCP (모델 Context Protocol) 서버는 Audacity를 mod-script-pipe로 제어합니다.

이 서버는 Audacity와 함께 파이프를 지정하고 MCP 도구로 많은 Audacity 스크립트 명령을 노출합니다.

특징

• mod-script-pipe를 통해 Audacity에 연결
• MCP 도구로 Audacity 명령의 넓은 세트를 노출
• stdio] 운송 (Codex/Claude/Desktop 클라이언트와 함께 작업)
• /tmp]의 자동 감지 파이프 스프릭스 (예 : .501)

요구 사항

• 평균 3.x+
• 파이썬 3.10+
• mod-script-pipe Audacity에서 활성화

설치

빠른 로컬 테스트 (MCP 호스트 필요 없음)

스크립트 대신 수동 설정을 선호한다면:

선택 (패키지 + CLI 엔트리포인트로 설치):

Audacity에서 mod-script-pipe 사용

1. Audacity를 여십시오.
2. 모듈 설정 페이지 열기:

• **윈도우/리눅스 **: Edit -> Preferences -> Modules -macOS: Audacity -> Settings... -> Modules (또는 [T8]])

3. mod-script-pipe] New] (또는 Disabled])에서 Enabled]를 설정합니다.
4. 나머지 Audacity.

참고: 현재 Audacity 버전에서는, Modules로 설정되어 별도의 "Scripting/Remote Control"섹션이 아닙니다.

Verify 관 존재:

Audacity MCP Server

MCP (Model Context Protocol) server for controlling Audacity through mod-script-pipe.

This server communicates with Audacity over named pipes and exposes many Audacity scripting commands as MCP tools.

Features

• Connects to Audacity via mod-script-pipe
• Exposes a broad set of Audacity commands as MCP tools
• Uses stdio transport (works with Codex/Claude/Desktop clients)
• Auto-detects pipe suffixes in /tmp (for example .501)

Requirements

• Audacity 3.x+
• Python 3.10+
• mod-script-pipe enabled in Audacity

Install

git clone https://github.com/An-3/mcp-audacity.git
cd mcp-audacity
./scripts/setup.sh

Quick local test (no MCP host needed)

# 1) Start Audacity and enable mod-script-pipe (see section below)
# 2) Verify local connectivity:
./scripts/smoke_test.sh

# 3) Start MCP server:
./scripts/run.sh

If you prefer manual setup instead of scripts:

python3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install "mcp[cli]>=1.6.0" "httpx>=0.28.1"

Optional (install as package + CLI entrypoint):

pip install .
audacity_mcp_server

Enable mod-script-pipe in Audacity

1. Open Audacity.
2. Open the Modules preferences page:
   • Windows/Linux: Edit -> Preferences -> Modules
   • macOS: Audacity -> Settings... -> Modules (or Audacity -> Preferences -> Modules depending on build)
3. Set mod-script-pipe from New (or Disabled) to Enabled.
4. Restart Audacity.

Note: In current Audacity versions, this is configured in Modules, not in a separate “Scripting/Remote Control” section.

Verify pipes exist:

ls -l /tmp/audacity_script_pipe.to.* /tmp/audacity_script_pipe.from.*

If the files are present, Audacity is ready.

Run the server manually

./scripts/run.sh

Expected startup logs include:

• Audacity MCP server starting up
• Opened Audacity mod-script-pipe
• Connected to Audacity mod-script-pipe

Connect from Codex

Add server to Codex MCP config:

codex mcp add AudacityMCP -- /absolute/path/to/mcp-audacity/.venv/bin/python /absolute/path/to/mcp-audacity/audacity_mcp_server.py

List configured MCP servers:

codex mcp list

Connect from Claude Desktop

Example claude_desktop_config.json:

{
  "mcpServers": {
    "audacity": {
      "command": "/absolute/path/to/mcp-audacity/.venv/bin/python",
      "args": [
        "/absolute/path/to/mcp-audacity/audacity_mcp_server.py"
      ]
    }
  }
}

Troubleshooting

• Failed to open Audacity pipes:
  • Confirm Audacity is running.
  • Confirm mod-script-pipe is Enabled.
  • Confirm pipe files exist in /tmp.
• spawn uv ENOENT:
  • Use absolute paths in client config, or use the Python command shown above instead of uv.
• Server starts but tools behave inconsistently: