Skip to main content
Glama
xDarkzx

AudacityMCP

by xDarkzx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to AudacityMCP

No user-submitted related servers found.

    Related Servers

    • audacity-mcp-max

      robworks-code
      A
      license
      B
      quality
      A
      maintenance
      Connects 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.
      100
      Apache 2.0

    • Audacity4MCP

      xDarkzx
      A
      license
      A
      quality
      A
      maintenance
      Enables 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.
      156
      2
      Apache 2.0

    • Audacity MCP Server

      jhonsu01
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      -

    • waves

      MirrorEdgeAI
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to analyze and repair audio files by viewing spectrograms, measuring noise, and applying fixes like healing hums or isolating speakers, all with undoable operations and without uploading audio.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 144 tools

    Disambiguation3/5

    Most tools are clearly distinct (project_, track_, label_, effect_ prefixes group by domain). However, there is notable redundancy and overlap: label_delete_audio_at vs label_cut_regions vs label_delete_regions vs label_split_regions vs label_silence_regions all operate on labeled regions with similar purposes. Similarly, cursor_to_track_end and select_cursor_to_track_end, and multiple label export functions (label_export, label_export_audio_segments, project_export_labels) create ambiguity about which to select.

    Naming Consistency4/5

    The naming follows a consistent verb_noun or category_verb pattern (project_, track_, label_, effect_, edit_, select_, cursor_, transport_, generate_, auto_). There are a few inconsistencies like 'normalize' and 'compressor' and 'limiter' and 'click_removal' that lack the effect_ prefix used by sibling tools, and 'get_noise_profile'/'noise_reduction' deviate from the pattern, but overall the convention is strong and predictable.

    Tool Count1/5

    144 tools is an extreme number for an audio editor MCP server. While Audacity is feature-rich, this surface is far beyond what agents can reasonably navigate. Many tools could be consolidated (e.g., the seven separate auto_cleanup_* pipelines, the large effect_* family, and the transcription set). This count will cause selection difficulty and cognitive overload for any agent.

    Completeness4/5

    The surface is quite comprehensive, covering project lifecycle (new/open/save/close/import/export), track management, selection, transport, editing, effects, generation, analysis, labeling, noise reduction, pipelines, and transcription. Minor gaps exist (no explicit record control for a specific track, no envelope editing beyond metadata, no undo/redo tools), but overall the domain is well covered for a full audio editing workflow.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources