Skip to main content
Glama
adepssimius

suunto-mcp

by adepssimius
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to suunto-mcp

No user-submitted related servers found.

    Related Servers

    • ClaudeCyclingMCP

      elias-ramzi
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that converts structured cycling workout specs into MyWhoosh .zwo and Garmin Connect workout files, with tools for validation, description, and rendering. It also includes skills for uploading workouts to both platforms.
      6
      MIT

    • 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
      -

    • garmin-mcp

      aapiskotin
      A
      license
      A
      quality
      C
      maintenance
      Enables creating, previewing, scheduling, and managing Garmin Connect workouts, plus reading activities and health metrics, all through a local MCP server.
      11
      MIT

    • intervals-mcp

      ale7canna
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for intervals.icu that reads training data (activities, wellness, calendar) and creates structured workouts on the calendar, which are pushed to devices like Garmin, Wahoo, Zwift, Coros, Suunto via the official API.
      10 npm
      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

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: preview_workout compiles and validates without uploading, list_workouts retrieves stored workouts, and describe_backend reports backend capabilities. There is no ambiguity or overlap between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: preview_workout, list_workouts, describe_backend. This is predictable and easy to navigate.

    Tool Count4/5

    With only 3 tools, the server is at the lower end of the ideal range, but each tool earns its place. The count feels slightly thin for a full workout management workflow, yet is appropriate for a focused validation and overview server.

    Completeness2/5

    The server lacks core operations such as create, update, delete, or upload for workouts. It only supports previewing and listing, with describe_backend to check capabilities, leaving significant gaps for any actual modification or synchronization workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources