REW MCP Server
Related Servers
Alternatives to REW MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables Claude to control Room EQ Wizard, analyze room acoustics measurements, and receive step-by-step guidance for calibration, treatment, speaker placement, and EQ validation.2733 npmMIT
- AlicenseNot gradedqualityDmaintenanceDynamically generates MCP tools from OpenAPI specifications, enabling AI assistants to interact with any REST API through natural language. Supports multiple APIs with authentication, parameter validation, and integration with Claude Desktop and LangChain.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude and other MCP clients to control Reason 13 through the documented Remote control-surface API, including transport, tempo, track selection, mixer channels, device parameters, note playback, and automation recording. It reports mapped controls and current values so an agent can make closed-loop parameter changes without patching or injecting into Reason.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables voice assistants to start, monitor, message, and approve local Claude Code sessions on your computer, including sessions already open in a terminal. It exposes session management, recaps, approvals, and history search as MCP tools.7GPL 3.0

sonora-mcpofficial
AlicenseNot gradedqualityBmaintenanceMCP server that wraps the Multiroom Audio Hub v2 REST API, providing 24 tools to control multiroom audio systems. Enables AI assistants to manage inputs, outputs, groups, routes, playback, and master mute.AGPL 3.0- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients to manage, run, and interact with local or cloud LLM models through exposed tools for listing, pulling, generating, chatting, embeddings, and web search/fetch. Supports Claude Desktop, Cline, and hybrid local/cloud setups.812 npmAGPL 3.0
TDQS
Scored across 16 tools
The measurement-specific, array codec, export/output and status tools are distinct. However rew_call_api, rew_request and rew_command all execute REW operations with subtle boundaries, and rew_batch also overlaps by running API workflows. Descriptions help, but an agent may still hesitate among the generic execution tools.
All tools share the rew_ prefix and snake_case formatting, with mostly verb_noun forms such as rew_list_measurements and rew_get_measurement. A few names are bare nouns or actions like rew_status, rew_request, rew_command and rew_batch, so the pattern is mostly consistent rather than perfect.
Sixteen tools is slightly above the ideal 3–15 range, but it is reasonable for a broad REW surface needing discovery, execution, measurement helpers and output handling. No tool appears wholly redundant, though the generic execution cluster adds some weight.
Measurement lifecycle is well covered through list/get/analyze/export, and API discovery plus generic execution can reach most REW operations. Generic call/request/command fill most gaps, though there is no explicit delete/rename/import tool and workflows rely on the generic surface.