Skip to content

TwelveTake-Studios/reaper-mcp

v1.3.1 Breaking

This release includes breaking changes for platform teams planning a safe upgrade.

Published 1mo MCP Developer Tools
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ai claude daw mastering mcp midi
+4 more
mixing model-context-protocol music-production reaper

ReleasePort's take

Light signal
editorial:auto 1mo

Release v1.3.1 fixes six broken MIDI and tool APIs, updates timing parameters for note‑adding functions, enables direct script execution, and adds several new FX manipulation features.

Why it matters: Fixes critical API failures (create_midi_item, add_midi_note, etc.) and introduces position‑controlled FX insertion; adopt if using these tools before the June 2026 release date.

Summary

AI summary

Fixed several broken MIDI and tool APIs, added new FX manipulation tools.

Changes in this release

Feature Low

Added `track_fx_add_by_name` with optional `position` argument to insert FX anywhere in a track’s chain.

Added `track_fx_add_by_name` with optional `position` argument to insert FX anywhere in a track’s chain.

Source: llm_adapter@2026-06-11

Confidence: high

 —
Feature Low

Added `track_fx_move` to reorder FX within a track’s chain.

Added `track_fx_move` to reorder FX within a track’s chain.

Source: llm_adapter@2026-06-11

Confidence: high

 —
Feature Low

Added `get_track_peak_hold` and `clear_all_peak_indicators` for peak‑hold metering.

Added `get_track_peak_hold` and `clear_all_peak_indicators` for peak‑hold metering.

Source: llm_adapter@2026-06-11

Confidence: high

 —
Feature Low

Added `get_track_master_send` and `set_track_master_send` to control master/parent sends.

Added `get_track_master_send` and `set_track_master_send` to control master/parent sends.

Source: llm_adapter@2026-06-11

Confidence: high

 —
Bugfix Medium

`add_midi_note` and `add_midi_notes_batch` now accept musical timing in beats (`start_beat`, `length_beats`) instead of PPQ.

`add_midi_note` and `add_midi_notes_batch` now accept musical timing in beats (`start_beat`, `length_beats`) instead of PPQ.

Source: llm_adapter@2026-06-11

Confidence: high

 —
Bugfix Medium

Removed module‑level `__name__` override that prevented direct execution of `python reaper_mcp_server.py`; script now starts correctly.

Removed module‑level `__name__` override that prevented direct execution of `python reaper_mcp_server.py`; script now starts correctly.

Source: llm_adapter@2026-06-11

Confidence: high

 —
Bugfix Medium

Fixed six broken tools: create_midi_item, add_midi_note, add_midi_notes_batch, get_midi_notes, get_item_info, set_item_* and get_track_peak now route through explicit bridge handlers.

Fixed six broken tools: create_midi_item, add_midi_note, add_midi_notes_batch, get_midi_notes, get_item_info, set_item_* and get_track_peak now route through explicit bridge handlers.

Source: llm_adapter@2026-06-11

Confidence: low

 —
Bugfix Low

Fixed several broken API tools to route through explicit bridge handlers.

Fixed several broken API tools to route through explicit bridge handlers.

Source: granite4.1:30b@2026-06-11-audit

Confidence: high

 —
Full changelog

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

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track TwelveTake-Studios/reaper-mcp

Get notified when new releases ship.

Sign up free

About TwelveTake-Studios/reaper-mcp

MCP server enabling AI assistants to control REAPER DAW for mixing, mastering, MIDI composition, and full music production with 129 tools

All releases →

Related context

Earlier breaking changes

  • v1.3.2 `render_project` now requires an explicit `overwrite` parameter to allow file overwriting.

Beta — feedback welcome: [email protected]