reaper-dev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP/SSE server. Default is 3000. | 3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_function_infoB | Get detailed information about a function from JSFX, ReaScript, or ReaWrap API |
| search_functionsC | Search for functions across JSFX, ReaScript, or ReaWrap APIs |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| JSFX Fundamentals | Core JSFX concepts: parameter indexing, slider visibility, @sections, memory management |
| REAPER Parameter System | How REAPER's parameter system works: types, reading, setting, named config params |
| Parameter Modulation (plink API) | REAPER's parameter linking system: local vs global indices, creating/reading links |
| FX Container System | Working with container FX: pointers, GUIDs, parent/child navigation |
| ReaWrap API Reference | Reference documentation for ReaWrap's object-oriented API |
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.