Skip to main content
Glama
rachittshah

trucksim-mcp

by rachittshah

Related Servers

Alternatives to trucksim-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to access live Elite Dangerous game context such as location, route, ship loadout, and journal history through local MCP tools, with an optional GitHub relay for remote access.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Local MCP server that connects Claude Desktop with Garmin and Apple Health data to read training and recovery, estimate heart rate and pace zones, analyze performance, and create structured workouts.
      22
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      MCP server combining TeslaMate historical analytics with Fleet API live data and commands. Works with Claude Code, Claude Desktop, Cursor, and any MCP-compatible client.
      29
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      This MCP server provides real-time integration between Elite Dangerous and Claude Desktop, enabling AI-powered analysis of your gameplay data and dynamic generation of EDCoPilot custom content.
      2
      MIT

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool targets a distinct aspect of the truck state (speed, fuel, navigation, job, etc.), but there is some overlap: get_truck_state includes speed/fuel while check_speeding and get_fuel_status focus on those specifically. Descriptions clarify the focus, so agents can generally select correctly.

    Naming Consistency3/5

    Most tools follow a get_ verb pattern, but check_speeding and list_recent_events break the convention with different verbs. This is more than a minor deviation, though still readable and predictable overall.

    Tool Count5/5

    With 10 tools, the server is well-scoped for a truck telemetry/monitoring purpose. Each tool has a clear role, and none feel redundant or missing at this granularity.

    Completeness4/5

    The tool set covers a broad range of truck and driver status (state, navigation, fuel, job, speeding, eco, trip, rest, events, raw data). Missing operations like historical queries or filtered events are minor gaps that most workflows can work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues