Skip to main content
Glama
Packi1992

CalisthenicsCompanion-MCP

by Packi1992
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to CalisthenicsCompanion-MCP

No user-submitted related servers found.

    Related Servers

    • set-and-signal

      aranlucas
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to connect to a privacy-first, self-hostable workout planning and training log, allowing coaching agents to preview and apply program changes while accessing training data through OAuth-protected endpoints.
      AGPL 3.0

    • sisrun-mcp

      cdutr
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to read your SisRUN training plan with your own credentials and answer questions about prescribed workouts, like weekly coach plans, in a structured format.
      3
      MIT

    • Trainner AI MCP Server

      abrahamhm00
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to access and analyze biometric and training data via MCP, supporting queries on sleep, performance, nutrition, and training load to generate adaptive training insights.
      -

    • apeiron-mcp

      Apeiron-Life
      F
      license
      B
      quality
      C
      maintenance
      Exposes client health data through a consolidated tool surface covering sleep, exercise, nutrition, cardio, fitness, cognitive, lifestyle, trends, notes, and chat history. Enables LLMs to retrieve time-series vitals, periodic assessments, unstructured text, and rolled-up summaries via standardized envelopes.
      11
      -
    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.3/5.0

    Scored across 19 tools

    Disambiguation4/5

    The read-path tools (get_training_state, get_stats, get_adherence, get_progress, get_history) share statistical scope, but each has explicit carve-outs for what it does and does not return, which prevents serious misselection. The propose_* and suggestion tools are cleanly distinct from each other and from the reads.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: get_* for reads, list_* for collections, propose_* for proposals, set_* for parameters, and withdraw_* for the one mutating exception. There is no mixed casing or vague verb usage.

    Tool Count4/5

    At 19 tools, the server is slightly above the ideal 3-15 band, but the count is justified by the breadth of the coach workflow: reads, analytics, parameters, proposals, and suggestion management. The set feels dense rather than bloated.

    Completeness5/5

    The tool surface covers the full coach workflow: raw history, computed training state, adherence, progress, templates, planned workouts, catalog, coach parameters, and proposal-based changes for plans, exercises, and calendar events, plus suggestion lifecycle management. Intentional gaps like accept/reject are external to the MCP boundary and clearly documented.

    Resources