Skip to main content
Glama
FindBPM tempo planning MCP

FindBPM tempo planning MCP

by Content-true

FindBPM tempo planning MCP

Local calculations that help use results from FindBPM, the browser-based BPM and key finder. FindBPM analyzes MP3, WAV, FLAC, and M4A audio on your device; this server never receives audio or performs audio analysis.

  • tempo_timing converts a known BPM into milliseconds per beat, eighth and sixteenth notes, and bar, plus half/double-time readings.

  • compare_tempos compares two reported rates and checks whether one may be a half/double-time interpretation of the other.

  • camelot_neighbors lists common nearby Camelot codes for a known key estimate.

  • get_official_links returns the official analyzer.

After you find bpm for a track, tap along to confirm whether the reported pulse is the beat you hear. At 120 BPM, one beat is 500 ms and a four-beat bar is 2 seconds. For a DJ transition, tempo and neighboring Camelot codes can narrow candidates, but listen to phrasing and harmony before using a mix.

Run

Node.js 20.18.1 or newer:

npm install
npm test
node index.mjs

Configure your MCP client to start node /absolute/path/to/findbpm-mcp/index.mjs over stdio. No account, audio file, or network request is needed by this server. MIT license; see LICENSE.

Available Tools

4 tools
camelot_neighborsFind nearby Camelot codesB

List common neighboring Camelot wheel codes for a known key estimate.

Inputs: code (required).

compare_temposCompare two temposB

Compare reported BPMs including half-time and double-time interpretations.

Inputs: firstBpm (required), secondBpm (required).

tempo_timingConvert BPM to timingB

Convert a known BPM to beat, subdivision, and bar lengths. Audio is not accessed.

Inputs: bpm (required), beatsPerBar.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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 recent community issues

    Related MCP Connectors

    Related MCP Servers

    • 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
    • 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
    • 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