Skip to main content
Glama
Lory97

Tag-per-Track

by Lory97
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Tag-per-Track

No user-submitted related servers found.

    Related Servers

    • beatlyzer-mcp

      Profazia
      A
      license
      Not graded
      quality
      C
      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

    • rootvine-mcp

      RagingOrangutan
      A
      license
      A
      quality
      A
      maintenance
      Cross-platform music link resolution for AI agents. Resolve any song or album across Spotify, Apple Music, Amazon, YouTube, and more. Returns affiliate-ready links with click tracking
      5
      63 npm
      3
      MIT

    • TrackTag MCP Server

      adigold
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to analyze local or URL-hosted audio files with TrackTag, returning professional music metadata such as BPM, key, genres, moods, and 35+ fields. Runs locally on your machine, using your TrackTag API key and credit balance for analyses.
      5
      23 npm
      1
      MIT

    • Audio Sonic MCP

      ripunjay-kashyap
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables local, private analysis of YouTube URLs and local audio files to extract BPM, key modulations, vocal presence, transient punch, stereo width, and CLAP vibe embeddings, returning structured sonic signatures for AI agents and CLI users.
      4
      MIT
    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

    A3.9/5.0

    Scored across 4 tools

    Disambiguation3/5

    analyze_audio and analyze_audio_with_lyrics are effectively aliases since lyrics extraction can be toggled via a parameter, creating avoidable overlap. The batch and artist stats tools are clearly distinct, so the ambiguity is limited but still real.

    Naming Consistency5/5

    All tool names use a consistent lowercase snake_case verb_noun structure: analyze_audio, analyze_audio_with_lyrics, analyze_audio_batch, lookup_artist_stats. The naming pattern is predictable and easy for an agent to infer.

    Tool Count4/5

    Four tools is within a reasonable scope for an audio analysis server, but one of them is redundant with analyze_audio. Removing the alias would make the count feel tighter and more purposeful.

    Completeness4/5

    The core workflows are covered: single-track analysis, lyrics extraction, batch processing, and artist stats lookup. Minor gaps exist, such as analysis history or playlist-level operations, but they are not obvious dead ends for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources