Related Servers

Most tools have descriptive names and descriptions that explicitly cross-reference alternatives (e.g. 'Prefer items_apply for multiple', 'Prefer configure_tracks for batch'), but there is heavy near-duplication: single-vs-batch pairs for tracks/items/markers/MIDI, six overlapping setup_* helpers (setup_fx_chain, setup_effect_bus, setup_vocal_chain, setup_parallel_compression, setup_drum_bus, setup_sidechain), three engine_* mixers (engine_mix, engine_fix_mix, engine_master), and three project-notes/metadata readers with subtle distinctions. An agent can usually find the right tool, but the boundaries between engine_mix and engine_fix_mix, or between setup_fx_chain and the specialized setup_* wrappers, are genuinely easy to confuse.

Domain prefixes are mostly predictable (track_, item_, fx_, midi_, send_, marker_, project_, transport_, selection_), but the verb placement is inconsistent: track_set_volume and fx_get_params are noun_verb, while add_markers_batch and markers_apply are verb_noun and stray from the marker_ prefix. Many strays also exist outside the prefix scheme (configure_tracks, setup_sidechain, compose_arrangement, chop_pipeline, bounce_stems, engine_mix, load_loops), giving mixed conventions overall while remaining readable.

174 tools is an extreme mismatch for a single MCP surface — far beyond the 3-15 sweet spot and well past even the 25+ 'too many' threshold. The sheer volume makes discovery and correct selection costly for an agent, regardless of how good individual descriptions are.

The surface is unusually thorough: CRUD for tracks, items, takes, MIDI notes/CCs, FX chains, sends, markers/regions, tempo, envelopes, plus transport, rendering/export, project save/backup/undo, and scripting. Gaps are minor — e.g. no bulk marker clear-all, no explicit automation-mode/VCA tools — but nothing that would obviously block a core REAPER workflow.