Skip to main content
Glama
ratho13

aidoo-mcp-server

by ratho13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to aidoo-mcp-server

No user-submitted related servers found.

    Related Servers

    • fitness-mcp-server

      ewongz
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides MCP servers for Claude to access fitness data from Strava and intervals.icu, enabling natural language queries for activity analysis, advanced training metrics, and wellness tracking.
      1
      -

    • evo-mcp

      jfelipembf
      F
      license
      B
      quality
      D
      maintenance
      MCP server for integrating with the EVO gym management API, enabling access control, member management, activity scheduling, sales, and workout management through natural language.
      12
      -

    • whoop-mcp

      Saadh05
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects Whoop fitness data to Claude, enabling natural language queries about recovery, sleep, workouts, and more.
      -

    • intervals-icu-mcp

      andiarenaleandro-ux
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that connects Claude to intervals.icu training data, enabling advanced physiological analysis, activity and wellness management, and conversational insights using proprietary metrics like CCI and HRV correction.
      MIT

    • hevy-coach

      jmilinovich
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that connects Claude to the Hevy fitness app, enabling AI-driven personalized strength coaching by reading lifting history and programming workouts.
      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

    B3.2/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear separation between list/get/create/update/cancel/delete operations. Even the convenience get_member_bookings and get_expiring_contracts are clearly distinct from their list counterparts by specific filtering intent.

    Naming Consistency4/5

    Tools follow a consistent aidoo_verb_noun pattern, but get is used for both single-item fetches and list-returning queries (e.g., get_expiring_contracts, get_member_bookings), while list is reserved for standard collection listings. This is a minor deviation from the ideal verb-per-action style.

    Tool Count3/5

    With 25 tools, the server is on the heavier side, covering multiple domain areas (members, contracts, bookings, checkins, etc.). While each tool has a purpose, the count feels large for a single server and might benefit from splitting into focused services.

    Completeness3/5

    The surface provides solid read coverage for all major resources and write operations for members, bookings, checkins, and webhooks. However, there is no create/update/delete for contracts, classes, trainers, or gyms, leaving notable lifecycle gaps for core domain objects.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources