# Tempo Tap Averager MCP for AI Agents MCP > Tempo Tap Averager calculates precise Beats Per Minute (BPM) and measures rhythmic stability using raw tap timestamps. It converts a simple sequence of taps into professional, measurable musical metrics, including suggested half/double time tempos and formal musical descriptors. ## Overview - **Category:** music - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_2CTRXzQJh12WHR77odG1YzNCClvHeoMY7D2mgQvz/mcp - **Tags:** bpm, rhythm, tempo, music-theory, audio ## Description Dealing with raw audio data or tap inputs can be messy. You've got a list of millisecond timestamps, but what does that actually mean musically? The Tempo Tap Averager solves that. This MCP lets your AI client take any sequence of taps and instantly calculate the precise tempo (BPM). It doesn't just give you one number; it suggests how that rhythm would sound in half-time or double-time. Furthermore, if you need to know how steady the beat is—if there are noticeable fluctuations or outliers—it generates a stability score for you. If you're writing music theory pieces, it even maps those BPMs to formal musical labels like 'Vivace.' Connecting this MCP via Vinkius gives your agent access to these deep rhythmic insights without needing complex audio processing libraries. You just give the taps; the system returns actionable musical data. ## Tools ### calculate_bpm It calculates the Beats Per Minute (BPM) from tap timestamps, giving you standard tempo, suggested half-time, and double-time versions. ### evaluate_rhythm_consistency This tool analyzes a tapped rhythm, providing a stability score between 0 and 1 and identifying the total number of timing outliers. ### get_tempo_metadata You give it a BPM, and it returns the corresponding formal musical label or term associated with that tempo. ## Prompt Examples **Prompt:** ``` I tapped out a beat sequence: [100, 350, 600, 850]. What's the tempo and how steady was it? ``` **Response:** ``` **Rhythm Analysis Report** * **Calculated BPM:** 200.0 (This is a strong metric.) * **Stability Score:** 0.98 (Excellent consistency! No major drift detected.) * **Outliers Detected:** 0 *Suggested Tempos:* Half-time: 100 BPM | Double-time: 400 BPM ``` **Prompt:** ``` What musical label should I use for a tempo of 165 BPM? ``` **Response:** ``` The musical term corresponding to 165 BPM is **Vivace**. *Definition:* Vivace means 'lively' or 'fast.' This suggests the piece needs high energy and rapid movement in its performance. This label helps set expectations for performers reading your score. ``` **Prompt:** ``` Check this tap sequence: [0, 450, 1200, 1800]. Is it rhythmically stable? What's the BPM? ``` **Response:** ``` **Tempo & Stability Metrics** * **Calculated BPM:** 133.33. * **Stability Score:** 0.65 (Moderate stability; there are noticeable timing variations.) * **Outliers Detected:** 2 (The gaps between the first and second taps, and the last two, show significant deviation from the average rate.) ``` ## Capabilities ### Derive Beat Per Minute (BPM) from Taps It takes a list of tap timestamps and calculates the exact BPM, providing suggested tempos for both half-time and double-time variations. ### Assess Rhythmic Stability You get an objective stability score (0 to 1) that tells you how consistent the tapped rhythm is, plus a count of detected timing outliers. ### Translate BPM into Musical Terms The system accepts a specific BPM and returns the corresponding formal musical descriptor, like 'Allegro' or 'Largo'. ## Use Cases ### Analyzing a Drummer’s Practice Session A user uploads raw tap data from a drum practice session. They ask their agent to check the rhythm's consistency, and the agent runs `evaluate_rhythm_consistency`, returning a score of 0.85 and flagging three major timing outliers that need correction. ### Setting Tempo for an Interactive Game A game developer inputs taps representing the desired beat pattern. The agent uses `calculate_bpm` to determine the precise tempo (120 BPM) and receives suggested tempos, allowing the developer to set difficulty levels accurately. ### Annotating Musical Scores A music student provides a sequence of beats. They ask what musical term applies, and the agent uses `get_tempo_metadata` on 140 BPM, instantly labeling it 'Allegro' for their coursework. ### Comparing Performance Variations A teacher wants to compare two different recorded performances. They run both through `calculate_bpm` to see the average tempo and then use `evaluate_rhythm_consistency` on each set of taps to grade their stability. ## Benefits - Get immediate, quantifiable musical metrics. Instead of guessing the tempo, use `calculate_bpm` to get the exact BPM and suggested half/double-time tempos. - Pinpoint rhythmic weaknesses instantly. The stability score from `evaluate_rhythm_consistency` tells you exactly how consistent a performance is, identifying specific timing outliers for correction. - Add professional context to your data. Use `get_tempo_metadata` to map any calculated BPM (like 140) directly to its musical label (e.g., Allegro), making your results sound polished. - Eliminate manual calculation time. Your agent handles the complex math of tempo variation, freeing you from tedious spreadsheet work and repetitive analysis. - Understand rhythm variations deeper than basic timing. The system doesn't just count taps; it assesses overall pattern stability, which is crucial for composing interactive music. ## How It Works The bottom line is you turn raw tap data into quantified musical metrics usable for composition or analysis. 1. You feed your agent a list of tap timestamps (in milliseconds) that represent the rhythm you want analyzed. 2. The MCP processes these raw data points, first calculating the base BPM and checking for rhythmic consistency by looking for timing deviations. It also checks if there are specific musical descriptors associated with that tempo. 3. Your AI client receives a structured output containing the precise BPM, a stability score, outlier counts, and any relevant musical labels. ## Frequently Asked Questions **How can Tempo Tap Averager help me analyze raw drum recording data?** Tempo Tap Averager quantifies your rhythm. Instead of just listening, you get a stability score and precise BPM figures that pinpoint exactly where the timing is off or if the tempo drifts over time. This gives you objective feedback for editing. **Does Tempo Tap Averager tell me what musical section I'm in?** No, it doesn’t identify sections, but it can give context to your BPM using `get_tempo_metadata`. If you know the tempo is 140 BPM, it tells you that the appropriate musical term is 'Allegro,' which helps label and categorize the music. **Is Tempo Tap Averager better than just counting taps for setting a beat?** Yes. Simple counting ignores timing variance. This MCP uses your exact millisecond timestamps to calculate BPM, giving you an average rate that is far more accurate and professional than a simple count. **What if my rhythm has slight variations in tempo? Will Tempo Tap Averager catch it?** Absolutely. That’s what the stability score does. It rates your rhythm's consistency (0 to 1) and counts specific outliers, letting you know exactly how much variation exists in the taps. **Can I use Tempo Tap Averager for music education purposes?** Yes. You can input a student’s performance data, calculate its precise BPM with `calculate_bpm`, and then give them objective feedback on stability using `evaluate_rhythm_consistency`.