Skip to main content
Glama
Sign In
tone-listener-mcp

tone-listener-mcp

by SimonKimDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to tone-listener-mcp

No user-submitted related servers found.

    Related Servers

    • beatlyzer-mcp

      Profazia
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to analyze audio files, extracting tempo, key, beat drops, volume surges, high tones, loudness, brightness, and structure, and returning structured JSON and visualizations.
      2
      MIT

    • boss-katana-mcp

      dogakocak
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to shape BOSS KATANA Gen 3 amplifier tones from natural-language descriptions, moving the knobs live inside BOSS TONE STUDIO over USB. Agents can read the current patch, set amp and effect parameters in one call, and let changes play through the amp instantly.
      6
      8
      MIT

    • Sonicproof

      kanaworksai-hue
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to check whether generated audio matches a prompt in any language, rank takes, run technical QC, judge fit against images or video, and search or dedupe a local sound library. Each tool returns the same JSON records as the matching CLI command, with the model loaded once and everything running locally.
      38 PyPI
      16
      MIT

    • daw-mcp-server

      ShokouP
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to read, patch, and render DAW projects (REAPER, FL Studio, .rpp/.dawproject) and to measure WAV audio metrics such as peak, RMS, LUFS, and stereo width. It closes the loop by applying patches, rendering before/after audio, and scoring the results against an intent so music-production models can be trained and verified.
      -
    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.9/5.0

    Scored across 4 tools

    Disambiguation3/5

    audio_metrics and analyze_audio both measure audio levels/spectrum and differ mainly by an optional Gemini upload step, which makes misselection likely. compare_audio and server_info are clearly distinct, so overlap is limited to one ambiguous pair.

    Naming Consistency3/5

    Names are readable but follow mixed conventions: two noun-style names (server_info, audio_metrics) and two verb_noun names (analyze_audio, compare_audio). No camelCase chaos, but there is no single predictable pattern for an agent to rely on.

    Tool Count4/5

    Four tools is a tight, focused surface for an audio-analysis server, and each tool maps to a plausible workflow. server_info is arguably filler, keeping it from a 5.

    Completeness3/5

    The surface covers measurement, single-clip analysis, and A/B comparison, but there is no tool for recording, streaming/live monitoring, or device/input selection despite the 'listener' framing. Agents would hit a dead end on any real-time or capture workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources