Robotics MCP Server
Related Servers
Alternatives to Robotics MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to develop VRChat worlds through a live Unity editor bridge: UdonSharp authoring and out-of-Unity linting, declarative scene assembly, spatial and budget audits, assets and open-licence fetching, ClientSim scenario verification, and local PC/Quest builds without a human in the editor.MIT
- 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 gradedqualityBmaintenanceProvides a runtime for autonomous virtual robot brains, sitting between game engines and LLM inference to offer perception ingestion, LLM-driven reasoning, episodic memory, personality engine, motor output, and multi-bot registry.2MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to author, inspect, compile, test, validate, build, and launch VRChat worlds through a typed Unity editor bridge covering UdonSharp, the VRChat SDK, ClientSim, assets, prefabs, animation, and profiling.2-
- AlicenseNot gradedqualityDmaintenanceEnables 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
- AlicenseAqualityDmaintenanceEnables controlling robots in ROS environments through natural language, supporting topics, services, actions, and GUI tools.2436MIT
TDQS
Scored across 25 tools
Tool boundaries are severely unclear: `robot_virtual` and `vbot_crud` both provide vbot CRUD, `robot_control` and `dreame_control` both expose Dreame vacuum commands, and `drone_control`, `drone_flight_control`, and `drone_navigation` overlap heavily on flight and mission management. The portmanteau-style operation lists make it hard for an agent to know which tool is canonical for a given action.
Most names are snake_case, but they do not follow a consistent action-oriented pattern: some use `_control`, some `_management`, some `_info`, some `_tool`, and some are arbitrary nouns like `robot_virtual`, `vbot_crud`, or `noetix_info`. This makes it difficult to predict tool names or to infer which tool will handle a specific operation.
The 25-tool count is at the heavy end of a reasonable range for such a broad robotics server, but several tools are near-duplicates or one-off info helpers. The set would be easier to navigate if the overlap-free core were consolidated.
The surface covers many important areas: virtual robot lifecycle, model management, workflow CRUD, Dreame vacuum controls, drone subsystems, and marketplace lookup. However, `robot_manufacturing` lacks concrete operations, sim backend lifecycle management is only partially exposed, and `robotics_agentic_workflow`/`environmental_logistics_handler` are opaque additions that create coverage gaps.