ROS MCP
Related Servers
Alternatives to ROS MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables large language models to interact with ROS robots seamlessly, allowing natural language control, real-time sensor monitoring, and autonomous task execution without modifying existing robot code.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables control of ROS/ROS2 robots through natural language commands by translating LLM instructions into ROS topics and services. Supports cross-platform WebSocket-based communication with existing robot systems without requiring code modifications.MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural language command control of robots via ROS2, with a web portal for real-time visualization and interaction.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI tools to interact with ROS2 robotics systems through natural language commands. Supports topic publishing/subscribing, service calls, message analysis, and auto-discovery of ROS2 interfaces for debugging and controlling robots.Mozilla Public 2.0
- AlicenseAqualityAmaintenanceConnects AI agents to ROS 2 robots via rosbridge, enabling observation, inspection, and control of robot topics, services, and actions through natural language.112MIT
- AlicenseNot gradedqualityDmaintenanceEnables robot navigation control and monitoring through natural language. Provides tools for robot positioning, navigation to coordinates, device status monitoring, task management, and emergency controls.MIT
TDQS
Scored across 24 tools
Each tool targets a distinct ROS 2 operation (e.g., call service, echo topic, launch simulation, list nodes). Despite some similar verbs like 'check' and 'get', the descriptions clearly differentiate the tools, leaving no ambiguity.
Tool names consistently use verb_noun pattern, but there is minor inconsistency in whether 'ros2' is included in the noun (e.g., 'list_topics' vs 'list_ros2_services'). This slight deviation from perfect uniformity justifies a 4.
With 24 tools, the set is comprehensive but slightly above the typical 3-15 range for well-scoped servers. However, each tool serves a clear purpose in the ROS 2 ecosystem, so it is not excessive.
The tool set covers major ROS 2 interactions: listing, publishing, service calls, actions, node info, and launching simulations. Minor gaps like a specific stop-node tool are absent, but agents can work around using 'clean_all_ros2_nodes' or other means.