Skip to main content
Glama
jfelipembf

evo-mcp

by jfelipembf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to evo-mcp

No user-submitted related servers found.

    Related Servers

    • hevy-mcp

      andreparmar
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that interfaces with the Hevy fitness tracking API, enabling AI assistants to manage workouts, routines, exercise templates, and more via natural language.
      26
      58,400 npm
      MIT

    • super-hevy-mcp

      stonelasley
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the Hevy workout tracker that enables users to query training history, log workouts, and manage routines via natural language.
      MIT

    • hevy-mcp

      rwestergren
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the Hevy fitness tracking app, enabling management of workouts, routines, exercise templates, folders, and webhooks through AI assistants.
      25
      58,400 npm
      MIT

    • Hevy MCP

      zachsai
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects AI clients to the Hevy workout tracking app, allowing users to manage routines and exercises. It enables reading workout history and logging new fitness sessions through simple natural language commands.
      -

    • aidoo-mcp-server

      ratho13
      F
      license
      B
      quality
      D
      maintenance
      MCP server for Aidoo fitness studio management software, enabling access to members, contracts, classes, bookings, and more directly from Claude.
      25
      -
    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.1/5.0

    Scored across 12 tools

    Disambiguation4/5

    Tools target mostly distinct resources and actions—member lookup, authentication, entry authorization, activities, carts, sales, and workouts are separable. Minor potential overlap exists between authenticate_member and authorize_entry, and between member listing and profile retrieval, but descriptions clarify the boundaries.

    Naming Consistency4/5

    Mostly snake_case with a verb_noun pattern (get_members, create_cart, enroll_member_in_activity), but health_check is a noun phrase and authorize_entry/authenticate_member vary slightly from the get_* style. Overall still readable and mostly predictable.

    Tool Count5/5

    12 tools is well-scoped for a gym/member API, with each tool mapping to a plausible operation. There is no obvious redundancy or excessive surface area.

    Completeness3/5

    The set covers read paths for members, activities, schedules, workouts, and sales, plus cart creation/retrieval, enrollment, entry authorization, and health checks. However, it lacks update/delete operations for members and activities, and cart item/checkout operations, leaving notable lifecycle gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources