A
licenseNot graded
qualityD
maintenanceMCP server that bridges Unity with AI agents, enabling scene inspection, C# code execution, and screenshot capture via WebSocket communication.
MIT
BeamNG MCP
by eric-rolph
Related Servers
Alternatives to BeamNG MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for AI agents to drive Gazebo / gz-sim simulation, with offline mock mode for CI/demos.4MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for safe OSRacer vehicle control, exposing ROS 2 and MCU serial surfaces through gated tools with preflight, arming, and emergency stop.-
- FlicenseNot gradedqualityCmaintenanceMCP server for controlling a simulated robot arm with vision-based pick-and-place, driven by LLM or manual control.1-
- AlicenseNot gradedqualityDmaintenanceA local MCP server that provides shared, real-time context across multiple AI agents via WebSocket and MCP resource notifications, enabling collaborative workspaces, memory, tasks, and messaging.8 npm2MIT
- FlicenseNot gradedqualityCmaintenanceFull-access MCP server for the Webots robot simulator that enables AI assistants to see, understand, and modify a running simulation, including scene-tree inspection/editing, robot control, viewport screenshots, and arbitrary code execution.-
TDQS
B3.2/5.0
Scored across 57 tools
Disambiguation5/5
Each tool targets a distinct operation (e.g., spawn vs. remove, attach vs. poll, scenario load vs. create). Domain prefixes (simulator_, vehicle_, map_, etc.) further reduce ambiguity, and even overlapping areas like AI control are separated into vehicle_ai_configure and autonomy_start/stop with clear dependency documentation.
Naming Consistency5/5
Tool names follow a consistent snake_case pattern with domain prefix followed by a verb or verb_noun (e.g., vehicle_spawn, map_object_list, autonomy_start). The convention is uniform across all 57 tools, with predictable verbs like get, set, list, create, update, delete.
Tool Count1/5
57 tools is far beyond the typical well-scoped range of 3–15 and even beyond the 'too many' threshold of 25+. Even for a complex simulation server, this many tools imposes a significant cognitive load and suggests poor modularization or inclusion of too many subdomains.
Completeness5/5
The tool surface comprehensively covers the BeamNG simulation ecosystem: connection, simulation control, environment, traffic, scenarios, vehicles, sensors, map objects and triggers, mod building and installation, job management, and autonomous driving. Essential operations (CRUD for vehicles, sensors, map objects; lifecycle for mods) are present, with no obvious gaps in the stated purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues