Skip to main content
Glama
TwelveTake-Studios

reaper-mcp

by TwelveTake-Studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
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
      B
      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
      30
      MIT

    • FenderStudioProMCP

      pajdarova
      A
      license
      Not graded
      quality
      B
      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.
      7
      MIT

    • 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

    C2.8/5.0

    Scored across 179 tools

    Disambiguation2/5

    The set contains numerous near-duplicate or overlapping tools: generic FX parameter setters coexist with high-level helpers (set_eq_band, add_eq, track_fx_set_param), and sidechain setup is split across create_send, setup_sidechain_send, configure_reacomp_sidechain, and setup_sidechain_compression. The 179-tool surface makes it hard to choose reliably, and render_region is explicitly a non-implemented alias, adding confusion.

    Naming Consistency3/5

    Names are overwhelmingly snake_case, but the convention is inconsistent: some put the resource first (track_fx_get_count, take_fx_get_param), others the verb first (get_track_count, set_track_volume), and there are parallel track_/take_ prefixes and mixed add/create/insert verbs. It is readable but not a single predictable pattern.

    Tool Count1/5

    179 tools is far beyond a well-scoped set for any single MCP server; even a broad DAW surface does not justify this many, and many are thin wrappers or convenience duplicates. The count alone makes the server unwieldy and difficult to navigate.

    Completeness4/5

    The surface covers project, track, item, take, MIDI, FX, routing, automation, rendering, markers, undo, and measurement, so lifecycle coverage is extensive. Minor gaps remain (e.g., no explicit master volume setter and a non-implemented render_region), but agents can work around them.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources