Hi everyone,
I’m trying to connect Claude Desktop to Audacity using the an3-audacity-mcp MCP server on Windows 10 and have hit a specific issue I can’t resolve. Hoping someone here has seen this before.
My setup:
— Windows 10 Pro (Version 10.0.26200)
— Audacity 3.7.7
— Python 3.14.5
— Claude Desktop (MSIX install, freshly installed as administrator)
What I’ve done correctly:
— Downloaded and extracted an3-audacity-mcp from GitHub
— Created a Python virtual environment and successfully installed all dependencies (mcp[cli]>=1.6.0 and httpx>=0.28.1) with no errors
— mod-script-pipe is set to Enabled in Edit → Preferences → Modules
— Confirmed mod-script-pipe.dll exists at C:\Program Files\Audacity\modules\mod-script-pipe.dll
— Confirmed via PowerShell (Get-Process) that mod-script-pipe.dll IS being loaded by Audacity
— Claude Desktop is installed and the claude_desktop_config.json is correctly configured with the right paths
— Tried toggling mod-script-pipe from Enabled → Disabled → Enabled and restarting Audacity each time
— Tried running Audacity as administrator
— Done a full system restart
The problem:
Despite mod-script-pipe.dll loading successfully into the Audacity process, no named pipe is being created. Specifically:
— Get-ChildItem \\.\pipe\ shows no audacity-related pipes
— Searching C:\Users\…\AppData\Local\Temp\ finds no audacity_script_pipe files
— Searching the entire C:\ drive finds no audacity_script files
Because no pipe is created, the MCP bridge has nothing to connect to, and Claude Desktop shows no hammer/tools icon.
My question:
Has anyone seen mod-script-pipe load but silently fail to create a named pipe on Windows 10? Is there a known fix or a way to diagnose why the pipe isn’t being created?
Any help would be greatly appreciated. Happy to provide more diagnostic info if needed.
Thanks!