Gizmos Audacity MCP
Related Servers
Alternatives to Gizmos Audacity MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLM-driven audio pipelines by controlling Audacity through mod-script-pipe, allowing generative audio, effects, and export via MCP tool calls.MIT
- AlicenseAqualityBmaintenanceEnables MCP-compatible AI assistants to control Audacity 4 locally for audio editing, effects, VST3 plugins, and cleanup pipelines via a TCP JSON-RPC bridge, with no cloud or API keys.15629 PyPI4Apache 2.0
- AlicenseBqualityCmaintenanceConnects any MCP-compatible AI assistant to Audacity, providing 132 tools for real-time audio editing, cleanup, mastering, and transcription — all running locally without cloud dependencies.100Apache 2.0
- AlicenseBqualityBmaintenanceEnables AI assistants to control Audacity for real-time local audio editing, mastering, and transcription through over 90 specialized tools. It allows users to perform complex audio processing tasks like noise reduction and podcast cleanup using natural language commands.144136Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to programmatically edit, analyze, and export audio projects through MCP tools, including multi-track editing, effects, transcription, and semantic search.1-
- AlicenseNot gradedqualityBmaintenanceEnables Claude to edit audio on Windows using the audio engine of the locally installed Audacity 4, covering splitting, trimming, converting, resampling, mixing, joining, inspecting, and chaining effects on files. It also installs an in-app Audacity 4 extension that adds export, split, import, and labeling actions directly to the editor's menus.1GPL 3.0
TDQS
Scored across 45 tools
Several clusters overlap: audacity_command, audacity_effect, audacity_pipeline, audacity_macros, and audacity_menu all execute processing or menu actions; audacity_measure, audacity_measure_file, audacity_compare_files, audacity_contrast, and audacity_loudness_target all measure audio; and the four label tools overlap. The descriptions are detailed and often say which tool to use when, but with 45 tools an agent can still misselect within these clusters.
All tools use the audacity_ prefix and lowercase snake_case, which is highly predictable. There is minor variation between action-first names (audacity_export, audacity_select) and noun-first names (audacity_track_set, audacity_labels_set, audacity_clip_move), but no chaotic mixed casing or prefixing.
The server exposes 45 tools, far above a well-scoped set, for a domain that is genuinely broad but also heavily fragmented into specialized measurement, label, diagnostic, lifecycle, and batch operations. Many individual tools are useful, but the total surface is heavy enough to make tool selection difficult.
Coverage is broad: project lifecycle, import/export, selection, track and clip editing, generating audio, effects, pipelines, labels, measurement, macros, transport, and batch processing are all represented. Minor gaps and deliberate limitations remain, such as no clipboard paste, restricted preference setting, and no undo entries for scripted effects, but most workflows have practical workarounds.