rebot-mhs-lab
Related Servers
Alternatives to rebot-mhs-lab
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to control Universal Robots through real-time connection management, status monitoring, and precise joint/linear motion control. Provides safe robot operation with built-in collision detection and simulation mode for development without physical hardware.6GPL 3.0

rebot-mcpofficial
AlicenseAqualityBmaintenanceEnables AI agents to control a reBot arm, capture reCamera snapshots and detections, and use motion, gripper, stop, and hand-eye calibration capabilities through a stdio MCP interface.24MIT- AlicenseAqualityBmaintenanceEnables LLM agents to safely inspect, plan, preview, and execute motions on ROS 2 manipulators, with server-enforced safety envelopes covering joint limits, workspace constraints, force/torque thresholds, rate limits, e-stop, human approval, and audit logging.2247 PyPIApache 2.0
- AlicenseAqualityCmaintenanceEnables AI agents to observe and control a browser-based 2D robot simulator, including driving, configuring sensors and modules, running programs, and generating wiring, firmware, and parts lists for ESP32, Arduino Uno, or Raspberry Pi.4188 npmMIT
- AlicenseAqualityCmaintenanceEnables AI assistants in MCP clients to read state and move a calibrated SO-101/SO-ARM101 robot arm through LeRobot, with per-joint safety limits, named poses, joint moves, and gripper controls.82MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control hardware devices like Arduino, Raspberry Pi, 3D printers, CNC machines, and custom robots via serial ports and HTTP. Provides tools for device discovery, command sending, sensor reading, servo control, G-code execution, and emergency stops with safety features.37 PyPIMIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: discovering metadata, reading state, writing state, triggering an emergency stop, and planning a two-arm handoff. There is no meaningful overlap that would cause an agent to select the wrong tool.
Most tool names follow a clear verb_noun pattern: discover_devices, read_device, write_device, plan_two_arm_handoff. The exception is emergency_stop, which is a noun-style command rather than a verb-prefixed action, making the set slightly inconsistent.
Five tools is a well-scoped size for this robotics lab server. Each tool covers a distinct operation and none feel redundant or extraneous.
The tool set covers device discovery, state reading, state writing, safety shutdown, and handoff planning. Minor gaps exist around explicitly executing a planned handoff or resetting a latched emergency stop, but these may be intentionally handled outside the MCP surface or through write_device.