Skip to main content
Glama
daredoole

audio-calibration-mcp

by daredoole
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to audio-calibration-mcp

No user-submitted related servers found.

    Related Servers

    • EvoBurrow MCP

      daredoole
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides 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.
      3
      MIT

    • sublevel

      drcano
      F
      license
      C
      quality
      B
      maintenance
      Enables 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
      -

    • chat-with-audio

      learningtour
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables chat-driven audio analysis and enhancement using local Claude, including denoising, EQ, compression, and loudness normalization, with an A/B viewer for synchronized comparison.
      1
      MIT

    • ananda-resonance

      FahadArfin
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables control of Equalizer APO profiles, filters, headphones, and diagnostics through MCP tools, allowing profile switching and audio management from any MCP client.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.4/5.0

    Scored across 101 tools

    Disambiguation4/5

    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 Consistency2/5

    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.

    Tool Count1/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources