Skip to main content
Glama
lewis-mcgillion

ProCyclingStats MCP Server

by lewis-mcgillion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ProCyclingStats MCP Server

No user-submitted related servers found.

    Related Servers

    • pcs-mcp

      MartinCeska
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server exposing ProCyclingStats teams, riders, and races data by scraping site pages, enabling custom rankings and historical result analysis.
      -

    • FirstCycling MCP Server

      r-huijts
      A
      license
      A
      quality
      D
      maintenance
      Provides professional cycling data from FirstCycling, allowing users to retrieve comprehensive information about cyclists, race results, historical cycling data, and team information through natural language queries.
      18
      19
      MIT

    • zwift-mcp

      benniblau
      F
      license
      Not graded
      quality
      B
      maintenance
      Exposes Zwift training history stored in a local SQLite database to MCP clients and a REST API, enabling queries for activities, power curves, race results, and training load.
      -

    • fantasypros-mcp

      dwooods
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to access FantasyPros data through tools for injury news, player lookup, consensus rankings, and projections.
      1
      MIT

    • mcp-chess

      pipeworx-io
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying Chess.com player profiles, ratings, game histories, and leaderboard rankings through a natural language MCP interface.
      2 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.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: discovering races, getting race overview, startlist, rider profile, stage results, and general search. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case, e.g., discover_races, get_race_overview, get_rider_profile. No deviations.

    Tool Count5/5

    6 tools is well-scoped for a cycling statistics server. Each tool covers a necessary operation without being excessive or insufficient.

    Completeness4/5

    The set covers core operations: race discovery, details, participants, rider profiles, stage results, and search. Missing team profiles and detailed rider season results, but the essential domain is covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources