Skip to main content
Glama
Spartan-Game-Studios

reaper-mcp-mac

by Spartan-Game-Studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to reaper-mcp-mac

No user-submitted related servers found.

    Related Servers

    • Scythe MCP REAPER

      yura9011
      F
      license
      B
      quality
      D
      maintenance
      Enables AI-powered music composition and control for REAPER DAW through OSC and ReaScript integration. Supports transport control, MIDI generation, track management, and music theory operations like scales, chords, and rhythm patterns.
      17
      -

    • 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
      109
      Apache 2.0

    • Logic Pro MCP Server

      MongLong0214
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents like Claude and Cursor to control Logic Pro for music production, including creating tracks, writing MIDI, operating transport and mixer, and inspecting live project data.
      161
      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
    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

    A3.7/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools are clearly separated by resource and action (tempo, track, MIDI item, FX, transport). The only potential confusion is reaper_get_project_state vs reaper_list_track_fx (both return state info) and reaper_call as an escape hatch could overlap with any dedicated tool, but descriptions mitigate this.

    Naming Consistency5/5

    All tools follow a consistent reaper_verb_noun pattern: reaper_ping, reaper_get_project_state, reaper_set_tempo, reaper_insert_track, reaper_add_midi_notes, etc. The naming is uniform and predictable.

    Tool Count4/5

    20 tools is on the higher end but appropriate for a DAW control surface covering project state, tracks, MIDI, FX, transport, and rendering. Each tool serves a distinct function, though a few could be consolidated (e.g., transport and edit cursor).

    Completeness4/5

    The toolset covers core DAW workflows: project state, track management, MIDI creation/editing, FX parameter control, transport, and rendering. Missing operations like track duplication, item deletion, or FX removal are notable but can be worked around via reaper_call.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources