Reaper MCP Server

by dschuler36

Overview Schema Source Related Servers Discussions Admin

Python

Local

Related Servers

Alternatives to Reaper MCP Server

No user-submitted related servers found.

Related Servers

reaper-mcp-server
Audio Processing Multimedia Processing
yeeking
A
license
Not graded
quality
D
maintenance
An MCP server that lets language models interact with the Reaper DAW
Updated 10 months ago (2025-11-23 18:00 UTC)
1
MIT
reaper-mcp
Audio Processing Multimedia Processing
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.
Updated 2 months ago (2026-07-12 21:57 UTC)
40
MIT
reaper-mcp
Audio Processing Multimedia Processing
T-Rzeznik
F
license
A
quality
C
maintenance
An MCP server that gives Claude Code (or any MCP client) full control of Reaper.
Updated 2 months ago (2026-07-15 00:41 UTC)
53
-
AbletonMCP
Audio Processing Multimedia Processing
fastmcp-me
A
license
B
quality
D
maintenance
Connects Ableton Live to Claude AI via the Model Context Protocol, enabling prompt-assisted music production, track creation, and Live session manipulation.
Updated a year ago (2025-10-12 16:00 UTC)
16
MIT
AbletonMCP
Audio Processing Entertainment & Media AI & Machine Learning
cliffc2
A
license
B
quality
D
maintenance
Connects Ableton Live to Claude AI through the Model Context Protocol, enabling AI-assisted music production and direct control of Ableton Live sessions.
Updated 3 months ago (2026-06-30 14:25 UTC)
100
MIT
AbletonMCP
Audio Processing Multimedia Processing
IMNMV
A
license
B
quality
D
maintenance
Connects Claude AI to Ableton Live via the Model Context Protocol, enabling prompt-assisted music production, track and clip manipulation, and session control.
Updated 9 months ago (2025-12-31 23:22 UTC)
16
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

C2.8/5.0

Scored 2026-08-25 03:25 across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: finding projects, parsing a project file, analyzing audio content, and listing installed plugins. There is no overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (find_reaper_projects, parse_reaper_project, analyze_audio_files, list_installed_fx). The naming is predictable and uniform.

Tool Count5/5

With only 4 tools, the server is tightly scoped to its apparent focus on Reaper project analysis and audio inspection. Each tool earns its place and the count feels appropriately minimal for the purpose.

Completeness4/5

The tool surface covers the core analysis workflow well: discovering projects, parsing their structure, analyzing audio files, and listing available FX. Minor gaps exist (e.g., no direct tool for editing or rendering), but for an analysis-oriented server the coverage is solid.