CarlaMCP
Related Servers
Alternatives to CarlaMCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables interactive design, execution, and analysis of SUMO traffic simulations through natural language, providing tools for scenario generation, policy experimentation, result analysis, and visualization.2610MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI interaction with embodied humans, autonomous vehicles, and drones through the HUTB simulator. Supports voice/chat control, weather conditions, perspective switching, and recording features.Apache 2.0
- AlicenseAqualityBmaintenanceEnables a language model to perceive a robot's surroundings, navigate to referenced objects, count instances, and stop when finished, via tools for viewing, grounding, driving, and counting.81MIT
- FlicenseNot gradedqualityCmaintenanceEnables scenario control, parking, sensor configuration and visualization, recording/playback, weather and traffic-light management for the customized CARLA UE5 simulator, with ROS 2 bag integration, through MCP tools and resources.2-
- AlicenseAqualityBmaintenanceAn agentic system for sim-ready interactive scene generation in Isaac Sim61Apache 2.0
- AlicenseNot gradedqualityCmaintenanceConnects LLMs to Eclipse SUMO traffic simulation, enabling AI agents to automate traffic network generation, demand modeling, signal optimization, simulation execution, and real-time TraCI control through natural language.53MIT
TDQS
Scored across 7 tools
Each tool has a clearly defined purpose with no overlap: server status, map listing, scenario generation from NL, replay, save, weather control, and validation. The pair run_scenario and replay_scenario are distinguished by input source (NL vs. saved spec).
All tools follow the verb_noun snake_case convention (get_status, list_maps, run_scenario, etc.), making the API predictable and easy to navigate.
Seven tools cover the essential operations for a CARLA simulation server: status check, map exploration, scenario lifecycle (create, save, replay, validate), and weather control. The count is well-scoped without redundancy.
The tool surface covers the core workflow (scenario generation, execution, replay, weather). Minor gaps include no tool to list or delete saved scenarios, but agents can work around by using the file system or naming conventions.