Skip to main content
Glama
tsutera09

Tempo MCP

by tsutera09
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Tempo MCP

No user-submitted related servers found.

    Related Servers

    • cadence

      rajanshxrma
      A
      license
      A
      quality
      C
      maintenance
      Provides Claude with real-time access to local health data including sleep, recovery, strain, and workouts from WHOOP and Apple Health, enabling informed context-aware interactions.
      6
      1
      MIT

    • Whoop MCP Server

      mohamedfaiz3020
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects your Whoop health data to Claude, enabling natural language queries about recovery, sleep, strain, and workouts.
      81 npm
      MIT

    • WHOOP MCP Server

      AimanElkhalifa
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to securely read your own WHOOP account data — recovery, HRV, resting heart rate, sleep, strain, workouts and body profile — through the official WHOOP developer API on a self-hosted server. Supports natural-language questions such as whether you are ready to train hard today.
      19 npm
      MIT

    • iClips MCP Bridge

      savimesmo
      F
      license
      Not graded
      quality
      D
      maintenance
      Connects iClips project data to Claude for agency capacity planning, exposing tools to monitor daily demand vs. capacity, stalled jobs, cascading off-work effects, and classification audits.
      -

    • Whoop MCP Server

      cbellbell-spin
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes Whoop fitness data (recovery, sleep, strain, workouts) to Claude for use as a daily training coach, enabling natural language queries about your health metrics and training readiness.
      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 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: scoring, check-in logging, revenue/calendar ingestion, recommendations, action application, history, digest, license management, and export. No two tools overlap in function, and descriptions make boundaries explicit.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (log_checkin, ingest_revenue_event, recommend_actions, apply_action), but a few like tempo_score, weekly_digest, and license_status are noun_phrases, slightly breaking the pattern. Still, all names are snake_case and readable.

    Tool Count5/5

    With 11 tools, the count is well within the ideal 3-15 range and each tool earns its place in the workflow—from data ingestion to scoring, recommendations, and administration. No redundancy or bloat.

    Completeness5/5

    The tool set covers the full domain lifecycle: input (check-in, revenue, calendar), analysis (tempo_score, recommend_actions), output (get_history, weekly_digest), execution (apply_action), and administrative functions (license_status, activate_license, export_data). Missing update/delete operations are not critical for this append-heavy logging use case.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources