Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.
AI-powered music production in REAPER through natural conversation - 173 tools across 26 modules covering transport, tracks, MIDI (insert/edit/quantize/humanize), mixing and FX (EQ, compression, sidechain, sends), tempo maps, markers/regions, ReaScript discovery/execution, and more.
TypeScript MCP server for OpenAI Images/Videos and Google GenAI (Veo) media generation, editing, and asset downloads.
Quality signal
47/100 (Fair)
41/100 (Fair)
Install path
pip · high
npx · high
Engagement
0 0 0 42
3 0 0 9
Tools
180 tools across 26 modules covering MIDI, FX, mixing, and transportLocal file-based Lua IPC bridge integration with REAPERSupports 35 style profiles for automatic genre-aware mixing/masteringVocal-chop pipeline and drum-pattern/chord-progression shorthandCompatible with any MCP client (e.g., Claude Desktop, Cursor, LM Studio)No cloud calls or data leaves the local machine
Full support for OpenAI Images API parameters for generation and editingComprehensive OpenAI Videos (Sora) job lifecycle managementGoogle GenAI Veo video generation with operation polling and downloadsSmart media fetching with resource_link or inline resource outputsStrict MCP spec compliance with typed CallToolResult outputsDebug tool for verifying MCP output shapes across clients
