Skip to main content
Glama
Machine-To-Machine

Formula One MCP Server (Python)

Related Servers

Alternatives to Formula One MCP Server (Python)

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      A local MCP server that gives Claude (or any MCP-compatible AI client) access to Formula 1 race data. Load any session from 2018 onwards, ask questions in natural language, and get answers backed by real telemetry, timing, and strategy data.
      4
      17
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time and historical Formula 1 racing data through the Model Context Protocol, offering access to timing data, driver stats, race results, telemetry, and more.
      15
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that provides comprehensive Formula One racing data, enabling access to event schedules, driver information, telemetry data, race results, and performance analytics through natural language queries.
      8
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for Formula 1 data via the FastF1 library. Ask Claude (or any MCP-compatible client) about race results, lap times, telemetry, standings, pit stops, and qualifying — with historical data back to 1950 via the Ergast API.
      21
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A high-performance personal Model Context Protocol (MCP) server built with the FastMCP Python framework.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      MCP server that provides F1 telemetry analysis, tyre degradation modeling, and pit strategy recommendations, delivering race engineer-style calls grounded in real data. It exposes tools for degradation fits, fuel correction, and strategy reasoning via LangGraph.
      4
      MIT

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    All 8 tools target distinct aspects of Formula One data—drivers, events, sessions, championships, and telemetry—with no overlapping functionality. Each has a clear, non-redundant purpose.

    Naming Consistency5/5

    Every tool uses a consistent verb_noun pattern with lowercase and underscores (e.g., get_driver_info, analyze_driver_performance). The naming is predictable and adheres to a single convention.

    Tool Count5/5

    With 8 tools, the server is well-scoped for its domain. It covers essential F1 operations without being too sparse or overly granular, making it ideal for most common queries without excessive complexity.

    Completeness4/5

    The tool set covers major areas: driver info, performance analysis, comparisons, standings, event details, schedule, session results, and telemetry. One minor gap is lack of team/constructor info, but the surface is otherwise comprehensive for a dedicated F1 server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues