Skip to main content
Glama
Content-true

FindBPM tempo planning MCP

by Content-true
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to FindBPM tempo planning MCP

No user-submitted related servers found.

    Related Servers

    • Set Planner

      shadowroommusic
      A
      license
      B
      quality
      B
      maintenance
      Enables DJs to calculate set runtime from cue points and transitions in provided track JSON, and to rank next-track candidates with explainable bpm, key, genre, energy scoring and warnings.
      2
      1
      AGPL 3.0

    • spotify-dj

      cikeyz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables DJs to retrieve BPM, key/Camelot, energy, and other track metadata with provider provenance, score transitions, plan setlists, and control Spotify playlists and playback with staged, revalidated writes for safety.
      MIT

    • midi-composer-mcp

      voho
      A
      license
      A
      quality
      B
      maintenance
      Provides atomic music-theory and MIDI tools for composing, enabling LLMs to chain deterministic steps like scale/chord lookups, degree resolution, rhythm generation, and MIDI rendering.
      13
      1
      MIT

    • youtube-music-mcp

      ElisonSz
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching YouTube Music and managing playlists through read and confirmation-gated write tools over STDIO. Supports identity checks, song search, playlist listing/retrieval, and previewed playlist creation, track addition, and exact track removal.
      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.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: timing conversion, BPM comparison, Camelot-neighbor lookup, and official-link retrieval. There is no meaningful overlap that would cause misselection.

    Naming Consistency4/5

    All names use snake_case, which is consistent and readable. However, the verb/noun pattern is mixed, with some tools named as noun phrases (tempo_timing, camelot_neighbors) and others as verb phrases (compare_tempos, get_official_links).

    Tool Count5/5

    Four tools is well scoped for a narrow tempo-planning server. Each tool contributes a distinct planning or reference capability without bloating the surface.

    Completeness4/5

    The set covers the core planning workflow: BPM-to-timing conversion, tempo comparison, Camelot-neighbor guidance, and a link to the official analyzer. Minor gaps remain around fuller key/Camelot conversion or additional tempo-planning utilities, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources