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
      B
      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
      533 PyPI
      12
      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.
      1
      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.
      173
      66
      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.7/5.0

    Scored across 176 tools

    Disambiguation3/5

    Most tools target distinct actions/resources, but overlapping convenience wrappers (add_eq vs track_fx_add_by_name, setup_sidechain_send vs setup_sidechain_compression) and a dead render_region tool create confusion. With 176 tools, high misselection risk exists even though descriptions are detailed.

    Naming Consistency4/5

    Almost all names use snake_case and a verb_noun/resource_verb pattern, with consistent families (track_fx_*, take_fx_*, midi_*). Minor deviations like get_track_num_sends vs track_fx_get_count and get_track_count keep it from perfect consistency.

    Tool Count1/5

    176 tools is an extreme over-expansion for any MCP server; each tool may be useful but the set is far beyond a well-scoped 3-15 tool surface.

    Completeness4/5

    The surface covers tracks, items, MIDI, FX, sends, automation, envelopes, project lifecycle, markers/regions, and rendering extensively. However, render_region is explicitly unimplemented and project save-as/close operations are absent, leaving minor dead ends.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources