Skip to main content
Glama
Sign In
OpenF1 MCP Server

OpenF1 MCP Server

by ragulhari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to OpenF1 MCP Server

No user-submitted related servers found.

    Related Servers

    • OpenF1 MCP Server

      commitNotFound
      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

    • OpenF1 MCP Server

      jimmyjoe009
      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.
      -

    • Pitwall F1

      darshjoshi
      A
      license
      C
      quality
      C
      maintenance
      Enables Claude to answer Formula 1 questions using real public data: race, sprint and qualifying results back to 1950, lap and sector times, 4 Hz car telemetry, tyre stints, pit stops and undercut strategy, plus locally drawn speed-trace and gear-shift plots. Also covers live session timing — positions, gaps, tyres, flags and weather — through 77 read-only tools that need no account, login or API key.
      77
      MIT

    • F1 MCP Server

      Josh-Mantel
      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
    • mcp-f1

      mcp-f1official

      pipeworx-io
      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.
      9 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

    B3.4/5.0

    Scored across 20 tools

    Disambiguation3/5

    Several tools overlap in practice: get_session_result and get_race_summary both return session classifications/standings, while get_stints and get_tyre_strategy both expose tyre-stint information. get_pit also partially overlaps with get_tyre_strategy because strategy includes pit stops. Descriptions help, but an agent could still misselect among these related tools.

    Naming Consistency5/5

    All tool names follow a clear snake_case verb_noun pattern, with get_* used for the vast majority and compare_fastest_laps as a natural action-specific variant. There is no mixing of camelCase, vague names, or inconsistent structural conventions.

    Tool Count4/5

    Twenty tools is slightly heavy, but the F1 data domain is broad and each tool maps to a recognizable data type or analysis operation. The count is reasonable for the scope, though some redundancy among result, tyre, and pit tools keeps it from being perfectly scoped.

    Completeness4/5

    The surface covers the core F1 workflow very well: meetings, sessions, drivers, results, championships, laps, stints, pits, positions, intervals, race control, weather, telemetry, location, and fastest-lap comparison. Minor gaps remain, such as no explicit team-radio tool and no standalone teams endpoint beyond championship context.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources