Skip to main content
Glama
jchan023

btwb-mcp

by jchan023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to btwb-mcp

No user-submitted related servers found.

    Related Servers

    • hevy-mcp-server

      RyK57
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to read and write Hevy workout tracking data, including workouts, routines, exercise templates, per-exercise history, and body measurements through all 15 Hevy public API endpoints.
      16 npm
      MIT

    • Iridium MCP Server

      RosTeHeA
      A
      license
      A
      quality
      B
      maintenance
      Connects AI agents to Iridium fitness data to query workout history, nutrition logs, and body measurements. It enables users to track exercise progress, training volume, and personalized trainer analysis through natural language.
      19
      26 npm
      1
      MIT

    • hevy-mcp-server

      adamdavies1915
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with the Hevy fitness tracking API, allowing users to log workouts, manage routines, browse exercises, and track fitness progress through natural language.
      16 npm
      MIT

    • hevy-mcp

      hmemcpy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables ChatGPT to read and manage one Hevy account's workouts, routines, exercise history, body measurements, and active workout drafts, including previewing and applying routine or workout changes with revision checks.
      18,616 npm
      Apache 2.0

    • Hevy Trainer MCP Server

      malikmobeen12
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants directly to Hevy workout data, enabling analysis of training volume, strength progression tracking, and web searches for fitness research.
      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

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: search_movement (library lookup) vs get_movement_history (per-set history), log_workout (single movement) vs log_rounds_workout (multi-movement rounds), get_workout_session (read) vs delete_workout_session (remove), plus a standalone auth utility. Descriptions proactively clarify overlaps, e.g. log_rounds_workout explicitly contrasts itself with log_workout.

    Naming Consistency5/5

    All seven tools use consistent snake_case verb_noun phrasing (search_movement, log_workout, get_workout_session, delete_workout_session, refresh_session_cookie). No style mixing or vague verb-only names.

    Tool Count5/5

    Seven tools is well-scoped for a workout-logging and movement-data integration; each tool earns its place with a clear role and no redundant entries.

    Completeness3/5

    The surface covers search, log (two variants), read, and delete, but has no update/edit for an already-logged result, and get_workout_session requires a known session ID with no search-by-date or list-sessions tool. Discovery of existing sessions/workouts is thus a notable gap.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources