Skip to main content
Glama

Related Servers

Alternatives to mcp-f1

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables access to Formula 1 data from the openF1.org API, including driver information, race results, lap times, telemetry, pit stops, weather conditions, and live position data across multiple seasons.
      -
    • A
      license
      C
      quality
      D
      maintenance
      Provides easy access to Formula 1 data including championship standings, event info, season calendars, track visualizations, session results, and driver/constructor info via FastF1 and OpenF1 API.
      17
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query real-time and historical Formula 1 data through the OpenF1 API, providing tools for driver info, lap times, telemetry, race events, and more.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Provides 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.
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides Formula 1 data via the Ergast API, enabling users to check current standings, get race results, view the season schedule, and look up driver profiles.
      28 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A real-time Formula 1 analytics server that lets you ask natural language questions about races, lap times, tyre strategies, pit stops, and more using live data from the OpenF1 API.
      -

    TDQS

    A3.5/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target clearly distinct F1 data endpoints (weather, laps, pit stops, car data, etc.), but get_drivers_championship and get_drivers_championship_view fetch the same standings with different rendering, which could cause selection confusion. get_race_replay_view also partially overlaps with position/location tools, though its replay purpose is described distinctly.

    Naming Consistency5/5

    All tools follow a consistent get_<resource> snake_case pattern (e.g., get_weather, get_drivers, get_laps). The two view tools add a predictable _view suffix, so the naming remains coherent and readable.

    Tool Count4/5

    20 tools is on the heavy side, but the F1 data domain is broad and each tool maps to a distinct OpenF1 endpoint or presentation layer. The count is reasonable rather than bloated, though it could be tightened by merging the championship view with its data tool.

    Completeness5/5

    The set covers the full OpenF1 read-only surface: sessions, meetings, drivers, results, grids, positions, laps, pit stops, stints, intervals, race control, overtakes, radio, telemetry, location, and both championships. The added view tools provide optional rendering without leaving obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues