Skip to main content
Glama
rifusaki

catence

by rifusaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to catence

No user-submitted related servers found.

    Related Servers

    • fitMCP

      gzarog
      F
      license
      Not graded
      quality
      B
      maintenance
      A multi-platform fitness MCP server that syncs data from Garmin, Strava, Google Fit, and Suunto into a local DuckDB database and provides analytics tools via MCP.
      1
      -

    • hybridlog

      Imgrund
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that mirrors your Garmin data into a personal database and exposes tools for health summaries, training load, muscle readiness, and race analysis, with optional chat-driven insights via stdio or HTTP.
      1
      MIT

    • garmin-mcp

      NoaMatout
      A
      license
      A
      quality
      B
      maintenance
      MCP server that lets you ask questions about your Garmin training history in plain language. It ingests FIT files into DuckDB locally and exposes typed tools for analyzing activities, streams, and summaries.
      9
      MIT

    • Garmin MCP

      lokranjanp
      A
      license
      A
      quality
      D
      maintenance
      MCP server that exposes Garmin Connect health and activity data (steps, sleep, stress, activities, etc.) via tools for querying, analysis, and visualization.
      17
      Apache 2.0
    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.4/5.0

    Scored across 35 tools

    Disambiguation4/5

    Most tools map cleanly to distinct resource/action pairs (e.g., describe_data vs describe_dataset, read_series vs aggregate_data). A few pairs like readiness_baseline/wellness_baselines and catence_status/catence_sync_progress could be confused, but their descriptions generally clarify the boundary.

    Naming Consistency4/5

    The vast majority of tools follow a consistent snake_case verb_noun pattern like review_*, get_*, describe_*, and hydrate_*. Minor deviations such as activity_decoupling, wellness_correlate, and catence_status keep it from a perfect 5, but the overall naming is predictable.

    Tool Count2/5

    At 35 tools, the surface is large and exceeds the 'too many' threshold for most agent-facing servers. Even for a broad athlete analytics domain, the selection burden is significant, and several related reporting tools could plausibly be consolidated.

    Completeness4/5

    The set covers the apparent athlete-analytics domain well: activity retrieval, series querying, statistical analysis, wellness metrics, cycling/swimming/running reports, sync control, and Strava enrichment. Minor gaps exist, such as no direct plan or nutrition detail tool despite search_context indexing those concepts, but core workflows generally resolve without dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources