Skip to main content
Glama
Sign In
assetto-corsa-mcp

assetto-corsa-mcp

by stormbuster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to assetto-corsa-mcp

No user-submitted related servers found.

    Related Servers

    • UnityMCP

      LANLightning
      A
      license
      D
      quality
      C
      maintenance
      Enables AI clients to control and inspect a Unity Editor through MCP tools for scene and play-mode operations, logs, screenshots, assertions, Lua execution, UI interaction, world observation, and bridge management; advanced UI/Lua/world features require project-specific adapters.
      41
      MIT

    • Blockland MCP

      Auios
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an MCP client to connect to a running Blockland client to execute TorqueScript, inspect player state, control character movement and actions, and capture screenshots.
      MIT

    • iRacing MCP Server

      ellettie
      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

    • omni-kit-mcp

      inbarajaldrin
      A
      license
      A
      quality
      C
      maintenance
      Enables driving Omniverse Kit apps (Isaac Sim, Isaac Lab) over MCP, allowing agents to control simulations, run Python, and call namespace-scoped tools via a single bridge.
      1
      3
      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.6/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct purposes: camera control is split cleanly into mode/free/look_at, and launch/quit/restore are clearly separated. The main overlap is between ac_get_state and ac_status, which both surface camera/car/time heartbeat data, though status adds process/bridge health.

    Naming Consistency4/5

    All names use a consistent ac_ prefix and snake_case, which is easy to scan. Minor deviations exist in ordering, mixing verb-first (ac_get_state, ac_set_time) with noun-first (ac_camera_mode, ac_material_get), but the pattern remains readable.

    Tool Count5/5

    At 15 tools the set is well-scoped for a game-control bridge, with each tool covering a distinct capability (camera, time, materials, lifecycle). No obvious filler tools.

    Completeness4/5

    The surface covers the full session lifecycle (launch, status, state, quit, restore configs) plus camera, time, screenshot, teleport, materials, and track config. Gaps exist around car input control (throttle/brake/steering) and replay manipulation, but core automation workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources