Skip to content

v1.3.1 — Community Fixes (thanks @nuxero)

Choose a tag to compare

View all tags
@david-cilluffo david-cilluffo released this 11 Jun 18:03
v1.3.1
46304ac

Community fix release — with thanks to Héctor Zelaya (@nuxero), whose PR #1 diagnosed the broken call paths and contributed several of the fixes and tools ported here. 158 tools total.

Fixed

  • create_midi_item, add_midi_note, add_midi_notes_batch, get_midi_notes, get_item_info, all six set_item_* tools, and get_track_peak were silently broken — they called raw REAPER API names through the bridge's generic fallback, which cannot resolve pointers from indices. All now route through explicit bridge handlers and are live-verified against REAPER 7.74.
  • add_midi_note / add_midi_notes_batch now use musical timing in beats (start_beat, length_beats) instead of PPQ — clearer for AI use. (Treated as a fix, not a break: the previous tools never worked.)
  • Removed the module-level __name__ override that prevented python reaper_mcp_server.py from starting directly (only the pip console script worked).

Added (from PR #1, @nuxero)

  • track_fx_add_by_name — optional position argument (insert anywhere in the chain).
  • track_fx_move — reorder FX within a track's chain.
  • get_track_peak_hold / clear_all_peak_indicators — peak-hold metering for gain staging.
  • get_track_master_send / set_track_master_send — control the master/parent send.

Note: update your installed bridge — copy the new reaper_mcp_bridge.lua over the old one and restart the script in REAPER.

Full changelog: https://github.com/TwelveTake-Studios/reaper-mcp/blob/main/CHANGELOG.md

Contributors

nuxero
Assets 2
Loading