Skip to main content
Glama

Related Servers

Alternatives to AI Race Engineer

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
      C
      maintenance
      An MCP server that provides 118+ Formula 1 analytics tools, enabling race analysis, driver comparisons, telemetry exploration, and strategy simulation through natural language.
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      MCP server for motorsport event documents, enabling AI agents to search, read, compare amendments, and parse schedules via typed tools.
      9
      -
    • F
      license
      A
      quality
      B
      maintenance
      Enables LLM-powered race engineers to compute Formula 1 pit-stop strategies from real session data, including tire degradation modeling, optimal pit windows, undercut/overcut simulation, and finish-position projection.
      9
      -
    • 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
      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

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools are largely distinct: session loading, stint data, degradation modeling, and multi-driver comparison. The only potential overlap is between get_degradation and compare_drivers, but the single-vs-multi-driver distinction is clear from descriptions.

    Naming Consistency4/5

    Three tools follow the 'get_' verb-noun pattern, while compare_drivers uses a different verb without 'get'. This is a minor deviation, but the names remain predictable and readable overall.

    Tool Count4/5

    With 4 tools, the server is well-scoped for its tyre-focused purpose. It covers the essential workflow without bloat, though it is on the smaller side, leaving room for additional specialized tools.

    Completeness4/5

    The server covers the full tyre degradation analysis lifecycle: session loading, stint retrieval, degradation fitting, and cross-driver comparison. Minor gaps like raw lap times or session context tools exist, but they are not critical for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues