Skip to main content
Glama
PrimeGoose

f1-telemetry-mcp

by PrimeGoose

Related Servers

Alternatives to f1-telemetry-mcp

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
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides Forza Horizon 5 telemetry tools (session listing, summaries, telemetry windows, tuning recommendations) to AI assistants, enabling natural language queries about driving sessions.
      -
    • A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to access real-time iRacing telemetry, race information, camera control, pit operations, and replay features through the MCP protocol.
      17
      1
      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
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to participate in a live 3D racing simulation by submitting race strategies, reacting to dynamic events, and observing full race state through MCP tools.
      -

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct analytical purpose, even when operating on similar underlying data. Lap timing tools are separated into listing, comparison, and fastest-sector extraction, while telemetry tools are separated into raw sample retrieval and braking-zone detection.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (get_*, compare_*, find_*). The verbs are predictable and accurately describe the action.

    Tool Count5/5

    Seven tools is a well-scoped set for F1 telemetry analysis. Each tool covers a distinct analysis need without obvious redundancy or bloat.

    Completeness4/5

    The surface covers session overview, lap timing, comparison, tyre wear, braking analysis, and raw telemetry. Minor gaps remain, such as weather, track position, stint/compound data, or pit-stop analysis, but core telemetry workflows are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues