Related Servers

Several tool pairs are nearly indistinguishable: edit_split_cut and edit_split_delete have identical descriptions ('leaves silence where audio was'), raw_paulstretch duplicates effect_paulstretch, project_export_labels overlaps label_export, and over 100 raw_* tools share the same boilerplate description with no guidance on selection. The multiple fade tools (effect_fade_in/out, effect_adjustable_fade, effect_studio_fade_out) and cursor-position tools (cursor_set_position, transport_set_cursor, raw_seek) further blur boundaries.

The curated tools mostly follow a consistent domain_action pattern (edit_, effect_, project_, track_, label_, generate_, transport_), but the ~120 raw_* tools use Audacity's internal command names with inconsistent formatting (raw_beatsand_measures vs raw_sel_cursor_stored_cursor). Standalone tools like compressor, limiter, normalize, truncate_silence, get_default_export_folder, and check_pipeline_status also break the established convention.

253 tools is an extreme count, far beyond any reasonable scope for an MCP server. Roughly half are raw_* pass-through commands for trivial UI actions (raw_cursor_left, raw_next_frame, raw_shift_up) that an agent would rarely need and that could be consolidated into a single parameterized command or removed entirely.

The surface covers the full Audacity domain: project lifecycle, track management, editing, 30+ effects, selection, labels, transport, analysis, generation, noise processing, mastering pipelines, and transcription. A few workarounds exist (label_delete_audio_at is a composite operation because Audacity lacks a native single-label delete) and transcription is experimental, but no major workflow is a dead end.