Skip to main content
Glama
TwelveTake-Studios

reaper-mcp

by TwelveTake-Studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to reaper-mcp

No user-submitted related servers found.

    Related Servers

    • reaper-mcp

      vecnode
      A
      license
      B
      quality
      D
      maintenance
      This MCP server enables AI assistants to control a live REAPER DAW instance, including transport, tracks, FX, MIDI, media, markers, rendering, and project state, with an escape hatch for arbitrary ReaScript commands.
      40
      MIT

    • PampaPilot MCP Server

      LeoLisena
      F
      license
      A
      quality
      D
      maintenance
      MCP server for controlling REAPER digital audio workstation from natural language. It enables AI agents to create tracks, import audio, adjust mix parameters, and manage sessions through typed operations and a REAPER bridge.
      22
      -

    • AbletonMCP

      wstierhout
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables AI assistants to control Ableton Live, providing 104 tools for music production including track, clip, device, and mixer control.
      156
      750 PyPI
      58
      MIT

    • reaper-mcp-bridge

      Echo722
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP-capable AI agents to control REAPER through typed tools and a Lua escape hatch for project creation, track management, recording and editing, MIDI writing, mixing, rendering, and batch operations.
      50
      1
      MIT

    • FenderStudioProMCP

      pajdarova
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that turns PreSonus Studio One into an AI-controllable DAW, enabling production workflows like editing, MIDI manipulation, mixing, effects, and export through an LLM.
      12
      MIT
    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

    C2.9/5.0

    Scored across 180 tools

    Disambiguation2/5

    While most tools have distinct targets, there are many overlapping areas: add_eq/add_compressor/add_limiter overlap with track_fx_add_by_name; setup_sidechain_send, configure_reacomp_sidechain, setup_sidechain_compression, and create_send all touch the same routing ground; render_region and save_fx_preset are dead tools that only return errors despite being listed. Detailed descriptions help some, but with 180 tools an agent will frequently misselect.

    Naming Consistency4/5

    Predominantly consistent snake_case verb_noun naming (get_track, set_tempo, add_marker, delete_region), with namespaced variants (track_fx_get_param, take_fx_set_enabled) that are still regular and readable. Minor deviations are bare-verb tools like play, stop, undo, redo, record, and pause, which break the verb_noun pattern but are inherently unambiguous.

    Tool Count1/5

    180 tools is far beyond any reasonable scope even for a DAW automation server, and several are known dead tools (render_region, save_fx_preset) that could be removed. Many parallel track/take FX param tools bloat the surface without adding distinct capability.

    Completeness4/5

    Very thorough coverage: project lifecycle, tracks, items, takes, MIDI editing, track/take FX, envelopes, routing/sends, markers/regions, rendering, measurement, selection, and undo. Gaps exist around take creation (only delete/explode/activate), master track volume/mute/solo set operations, and two tools that are explicitly not implemented.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources