audio-calibration-mcp
Related Servers
Alternatives to audio-calibration-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides a control room for inspecting A1 Evo AcoustiX artifacts, operating REW measurement workflows, coordinating calibration presets, and making allowlisted Denon/Marantz receiver changes with backups and verification.7MIT
- AlicenseAqualityCmaintenanceEnables natural language control of Room EQ Wizard for acoustic measurements, analysis, and EQ optimization, with peak/null detection and room-mode analysis.463MIT
- FlicenseCqualityBmaintenanceEnables reference-matching low-end mix analysis and adjustment in Ableton Live, including measurement, genre-scoped comparison, mix planning, safe apply/undo, and bass patch design toward a target.36-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read and adjust Windows HXAudio APO parametric EQ, preamp, virtual bass, and related DSP settings, with live registry-backed updates, backups, and PEQ curve imports.MIT
- AlicenseAqualityBmaintenanceAudio perception for AI agents. Measure loudness, clipping, noise and pitch; view spectrograms; split audio into events; transcribe speech; compare before/after; and clean up, edit or synthesize sound. Runs locally, no API keys.14MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables deterministic, zero-dependency audiological analysis of distortion-product emissions, SNR/clinical pass criteria, and outer hair cell fatigue scoring so agents can assess cochlear health and headphone noise overexposure.MIT
TDQS
Scored across 101 tools
Most tools have clearly distinct purposes, especially with the plan/execute pairs and specialized analysis functions. Some aliases and related analysis tools (e.g., rew_trace vs. rew_generate_trace) create minor ambiguity, but overall an agent can differentiate the tools.
Naming is inconsistent: many tools follow the verb_noun pattern with _plan/_execute suffixes, but aliases (rew_load_file, rew_save_all) and direct-action tools (rew_trace, audio_room_metrics) break the convention. While prefixes (audio_, rew_, car_, jamesdsp_) are consistent, the mixed style is confusing.
With 101 tools, the server is massively over-scoped for any MCP purpose. Even for a complex domain like audio calibration, this number overwhelms agents and makes tool selection error-prone. The typical range is 3–15, and this is far beyond that.
The tool surface is extremely comprehensive, covering measurement, analysis, EQ design, DSP, listening tests, uncertainty, room acoustics, and REW integration. Minor gaps exist (e.g., no artifact deletion or explicit update for some resources), but the workflows are largely complete.