FirstCycling MCP Server
Related Servers
Alternatives to FirstCycling MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceProvides professional cycling data from ProCyclingStats, enabling race discovery, stage results, rider profiles, startlists, and free-text search through MCP tools.63-
- AlicenseBqualityDmaintenanceProvides comprehensive Formula 1 data access including race schedules, session results, lap times, telemetry data, driver/constructor standings, and circuit information. Enables users to retrieve and analyze F1 racing data through natural language queries using the FastF1 Python package.5MIT
- AlicenseAqualityAmaintenanceProvides access to Formula 1 data including driver and constructor championship standings with support for current and historical seasons. Enables users to query F1 championship information through natural language with plans for expanded race data and telemetry.221MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to ask ChatGPT or Claude where a runner or cyclist is in a live race, how the race is going, and what the weather along the course will be, returning live maps and 3D route flyovers inline in the chat. Also surfaces cycling tour day-by-day routes, GPX links and organiser notes, all read-only and free.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server exposing ProCyclingStats teams, riders, and races data by scraping site pages, enabling custom rankings and historical result analysis.-
- AlicenseNot gradedqualityDmaintenanceProvides live Formula 1 data such as driver standings, race results, and schedule for the current season, enabling users to ask about F1 without stale training data.1MIT
TDQS
Scored across 18 tools
The tools have clear distinctions between race-focused and rider-focused operations, but there is significant overlap within rider tools. For example, get_rider_best_results, get_rider_grand_tour_results, get_rider_monument_results, get_rider_one_day_races, get_rider_race_history, get_rider_stage_races, and get_rider_year_results all retrieve subsets of race results, which could confuse an agent about which to use for specific queries. The descriptions help differentiate, but the boundaries are fuzzy.
All tool names follow a consistent snake_case pattern with a verb_noun structure (e.g., get_race_details, search_rider). The naming is predictable and readable throughout, with no deviations in style or convention, making it easy for an agent to parse and understand the tool purposes.
With 18 tools, the count is on the higher side for a cycling data server, bordering on heavy. While the domain of professional cycling is broad, the tool set includes many overlapping rider result tools that could potentially be consolidated, making it feel slightly bloated but still within a reasonable scope.
The tool surface covers the cycling domain well with race details, results, rider information, and search functionalities. However, there are minor gaps, such as no tools for team details beyond rider affiliations, race calendars, or live race data, which agents might need for comprehensive coverage. The core operations are well-represented, allowing agents to work around these omissions.