reaper-dev-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@reaper-dev-mcp What does the ReaScript function reaper.TrackFX_GetParam do?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Reaper Dev MCP Server
MCP (Model Context Protocol) server providing reference documentation for REAPER development, ReaScript API, JSFX programming, and ReaWrap API.
Purpose
This server provides static reference documentation that serves as a lookup reference for factual information about REAPER development. It helps prevent "token burn" by avoiding the need to rediscover common patterns and pitfalls in every session.
Related MCP server: SJ RedM MCP Server
Features
Queryable API Documentation: Use tools to search and get detailed function information
JSFX Fundamentals: Core concepts and gotchas
ReaScript API: Complete function reference with signatures and parameters (2,282 functions across C, EEL2, Lua, Python)
ReaWrap API: Object-oriented wrapper documentation (14 classes, 736 methods)
Installation
Quick Start
Choose your IDE and follow the instructions:
Claude Code CLI - Recommended, easiest setup
Cursor IDE - Works with stdio or HTTP
Claude Desktop - Requires HTTP server
Claude Code CLI
Prerequisites: Node.js v18+
Installation (one command):
claude mcp add --transport stdio --scope user reaper-dev -- npx -y reaper-dev-mcpVerify it's working:
claude mcp listYou should see: reaper-dev: npx -y reaper-dev-mcp - ✓ Connected
That's it! The server will automatically start when Claude Code needs it. Restart your Claude Code session to use the tools.
Cursor IDE
Cursor supports both stdio and HTTP transports. Stdio is recommended (no background process needed).
Option A: stdio Transport (Recommended)
Prerequisites: Node.js v18+
Open Cursor settings:
macOS/Linux:
~/.cursor/mcp.jsonWindows:
%APPDATA%\Cursor\mcp.json
Add this configuration:
{
"mcpServers": {
"reaper-dev": {
"command": "npx",
"args": ["-y", "reaper-dev-mcp"]
}
}
}Restart Cursor
That's it! Cursor will spawn the server automatically when needed.
Option B: HTTP/SSE Transport
If you prefer HTTP (or stdio doesn't work), use this method:
Start the server in a terminal (keep it running):
npx -y reaper-dev-mcpThe server will start on
http://localhost:3000. For a custom port:PORT=8080 npx -y reaper-dev-mcpOpen Cursor settings and add:
{
"mcpServers": {
"reaper-dev": {
"type": "sse",
"url": "http://localhost:3000"
}
}
}Restart Cursor
Note: The server must be running before Cursor starts.
Claude Desktop
Claude Desktop requires HTTP/SSE transport.
Prerequisites: Node.js v18+
Start the server in a terminal (keep it running):
npx -y reaper-dev-mcpThe server will start on
http://localhost:3000. For a custom port:PORT=8080 npx -y reaper-dev-mcpConfigure Claude Desktop:
Locate your config file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
Add this configuration:
{
"mcpServers": {
"reaper-dev": {
"type": "sse",
"url": "http://localhost:3000"
}
}
}Restart Claude Desktop
Note: The server must be running before Claude Desktop starts.
Development Setup
If you want to modify the server or contribute:
git clone https://github.com/Conceptual-Machines/reaper-dev-mcp.git
cd reaper-dev-mcp
npm install
npm run buildRun in development mode:
npm run devRun tests:
npm run testMCP Tools
get_function_info
Get detailed information about a function from JSFX, ReaScript, or ReaWrap API.
Parameters:
api(string): One of "jsfx", "reascript", "reawrap"function_name(string): Name of the function to look upclass_name(string, optional): Required for ReaWrap API queries
Examples:
// JSFX
{
"api": "jsfx",
"function_name": "sin"
}
// ReaScript
{
"api": "reascript",
"function_name": "TrackFX_GetParam"
}
// ReaWrap
{
"api": "reawrap",
"class_name": "track",
"function_name": "add_fx_by_name"
}search_functions
Search for functions across JSFX, ReaScript, or ReaWrap APIs.
Parameters:
api(string): One of "jsfx", "reascript", "reawrap"query(string): Search query (function name, description, etc.)limit(number, optional): Maximum number of results (default: 10)
Examples:
{
"api": "reawrap",
"query": "create",
"limit": 5
}Resources
All documentation is available as MCP resources:
reascript://jsfx-fundamentals- Core JSFX conceptsreascript://parameter-system- REAPER parameter systemreascript://parameter-modulation- Parameter linking (plink API)reascript://fx-containers- FX container systemreascript://reawrap-api- ReaWrap API reference
API Coverage
The MCP server provides access to:
JSFX API: 110 functions from official REAPER documentation
ReaScript API: 2,282 functions organized by language (C, EEL2, Lua, Python)
ReaWrap API: 14 classes with 736 methods
Success Criteria
✅ No More Token Burn: Stop rediscovering JSFX parameter indexing every session
✅ Fast Problem Solving: Quick lookup for plink API, container indices
✅ Prevent Regressions: Document all bugs so they're never repeated
✅ Reusable Knowledge: Can be used across all REAPER projects
License
MIT
Available Tools
2 toolsget_function_infoB
Get detailed information about a function from JSFX, ReaScript, or ReaWrap API
Inputs: api (required), function_name (required), class_name.
search_functionsC
Search for functions across JSFX, ReaScript, or ReaWrap APIs
Inputs: api (required), query (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: search_functions is for discovery/listing matching functions, while get_function_info retrieves detailed information about a specific known function. There is no overlapping functionality or ambiguity.
Both tool names follow the same verb_noun pattern: search_functions and get_function_info. The naming is predictable and consistent, making the tool surface easy to understand.
With only 2 tools, the server feels slightly thin, but it is focused on a narrow read-only domain (API function reference lookup). The count is borderline but not unreasonable for the stated purpose.
The domain is a read-only API reference for REAPER development. Search and get-info provide a complete workflow: discover functions through search, then retrieve detailed info. There are no missing CRUD operations or obvious dead ends.
Maintenance
Related MCP Connectors
Provide your AI coding tools with token-efficient access to up-to-date technical documentation for…
RedM / RDR3 docs MCP server: native lookups, semantic search, VORP, RSGCore, oxmysql.
Independent QBCore API, resource and troubleshooting docs with cited sources.
Kepler OGame bot: search its .ank scripting API, exact signatures and examples. Read-only, no key.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceProvides documentation lookup and search capabilities for FiveM development, including GTA V native functions, QBCore events, and ox_lib exports. Enables developers to query documentation and generate resource templates through natural language.-
- AlicenseBqualityDmaintenanceA unified development tool for RedM that provides access to RDR3 discoveries, framework documentation (VORP/RSGCore), native functions across 86+ namespaces, and database operations with smart context-aware loading.137MIT
- AlicenseNot gradedqualityCmaintenanceProvides access to HISE documentation, including UI component properties, Scripting API methods, and module parameters. It features a searchable database of code snippets and best practices to assist in audio software development.9MIT
- AlicenseBqualityAmaintenanceConnects AI assistants to REAPER for music production, enabling full control over tracks, MIDI, mixing, mastering, and audio analysis through 153 tools across 24 modules.174117Apache 2.0