Skip to main content
Glama
mishan

ac-race-engineer

by mishan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ac-race-engineer

No user-submitted related servers found.

    Related Servers

    • fastf1-mcp

      aashnakunk
      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.
      17
      1
      MIT

    • f1-telemetry-mcp

      PrimeGoose
      A
      license
      A
      quality
      B
      maintenance
      Gives AI assistants structured access to racing-game telemetry such as lap and sector times, lap comparisons, braking zones and tyre wear through MCP tools and resources. It works out of the box on bundled synthetic sample data and can ingest a live F1 23 UDP feed.
      7
      MIT

    • 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

    • trucksim-mcp

      rachittshah
      A
      license
      A
      quality
      A
      maintenance
      Streams live Euro Truck Simulator 2 / American Truck Simulator telemetry and driving analytics to any MCP-compatible AI assistant, with read-only tools for truck state, navigation, fuel, job status, speeding checks, eco scoring, trip summaries, rest advice, and recent events, plus a headless Claude coach agent.
      10
      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

    A3.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct function: recording control, live data, session/lap listing, lap analysis, driver notes/messages, and setup management. No two tools overlap in purpose, making it easy for an agent to select the correct one.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (start_recording, list_sessions, write_setup), but a few like recording_status, live_snapshot, and bridge_status deviate. This minor inconsistency does not hinder readability.

    Tool Count5/5

    With 14 tools, the server is well-scoped for a race engineer domain. Each tool covers a necessary operation without redundancy or unnecessary bloat, fitting the expected complexity.

    Completeness4/5

    The tool surface covers recording, analysis, communication, and setup management. Minor gaps exist (e.g., no tool to delete sessions or view raw telemetry), but the core workflow for a race engineer is fully supported.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources