Skip to main content
Glama
robworks-code

audacity-mcp-max

by robworks-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to audacity-mcp-max

No user-submitted related servers found.

    Related Servers

    • 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

    • AudacityMCP

      xDarkzx
      A
      license
      B
      quality
      A
      maintenance
      Enables 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.
      144
      101
      Apache 2.0

    • ReaperMCP

      xDarkzx
      A
      license
      B
      quality
      A
      maintenance
      Connects AI assistants to REAPER for music production, enabling full control over tracks, MIDI, mixing, mastering, and audio analysis through 153 tools across 24 modules.
      174
      84
      Apache 2.0
    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.3/5.0

    Scored across 132 tools

    Disambiguation2/5

    With 132 tools, there is significant overlap. For example, edit_split_cut and edit_split_delete both leave silence, and there are multiple fade effects (fade_in, fade_out, adjustable_fade, studio_fade_out) with unclear distinctions. Many auto_* pipelines share similar parameters and purposes, making it hard for an agent to select the correct tool.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern with underscores (e.g., select_cursor_to_track_end, effect_amplify, project_import_midi). There are no deviations or mixed conventions, making the naming predictable and easy to understand.

    Tool Count1/5

    132 tools is excessive for an MCP server, even for a comprehensive audio editor. Many tools could be parameterized or combined (e.g., all effects could be one tool with a type parameter, auto_* pipelines could be unified). This number overwhelms the surface and hinders agent decision-making.

    Completeness4/5

    The tool set covers a wide range of audio editing tasks: selection, editing, effects, analysis, generation, labels, tracks, transport, pipelines, and transcription. Minor gaps exist (e.g., no explicit chorus/flanger effects), but overall the surface is well-rounded for most audio editing workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources