Skip to main content
Glama
Darakhsh1999

Formula 1 MCP Server

by Darakhsh1999
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to Formula 1 MCP Server

No user-submitted related servers found.

    Related Servers

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

    • 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 by pipeworx-io

      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.
      266 npm
      MIT

    • Pitstop

      praneethravuri
      A
      license
      A
      quality
      A
      maintenance
      Provides 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.
      22
      1
      MIT

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

    C2.5/5.0

    Scored across 17 tools

    Disambiguation3/5

    Core F1 retrieval tools (standings, event info, session results, driver/constructor info) are clearly distinct. However, the OpenF1 API plumbing tools (get_api_endpoints, get_api_endpoint, get_endpoint_info, get_filter_info, get_filter_string, apply_filters, send_request) overlap heavily in purpose, and update_drivers/update_constructors have no descriptions, making their boundaries unclear.

    Naming Consistency4/5

    All tools share a consistent f1_mcp_server_ prefix and mostly use verb_noun or verb_resource naming (get_*, update_*). Minor deviations exist: championship_standings and track_visualization lack explicit verbs, and get_api_endpoint vs get_api_endpoints differ only by plural.

    Tool Count3/5

    17 tools is on the heavy side for an F1 data server. While core domain tools are justified, seven generic OpenF1 API access/filter tools appear to expose implementation plumbing rather than distinct user-facing capabilities, inflating the count.

    Completeness4/5

    The surface covers key F1 entities (drivers, constructors, standings, events, calendars, session results) and generic OpenF1 request tools provide fallback access to unmodeled data like laps, telemetry, or pit stops. Explicit list/search tools and clear update semantics are missing, but agents can work around most gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources