schunk_mechatronic_gripper_mcp_server
MCP server controlling SCHUNK EGU, EGK and EZU grippers through the running SCHUNK ROS 2 driver node, with tools to check driver state, discover grippers, configure and activate the driver.
Summary rewritten from the vendor site because the catalog version did not match it.
What it does and how it connects
The SCHUNK Mechatronic Gripper MCP Server controls SCHUNK EGU, EGK and EZU grippers. It is an MCP server that talks to the SCHUNK ROS 2 driver node over ROS 2; it does not start the driver itself, and the driver node must be running and available at /schunk/driver before the tools are used.
Setup runs through the MCP tools: check the driver state with get_driver_state, discover grippers with scan_grippers or add one directly with add_gripper, then configure the driver with configure_driver and activate it with activate_driver. The server needs Python 3.12 or newer, ROS 2, and the SCHUNK ROS 2 driver with its interface packages.
The repository ships a VS Code MCP configuration that starts the server through bash, sourcing the ROS 2 setup and the driver workspace setup first. The README points to the separate driver repository for gripper communication, network, serial-port and hardware setup.
Alternatives
Compare side by side- gantry-oss
A shared ledger for people and agents developing robot hardware and software, rather than an MCP server that drives SCHUNK grippers.
- agentic-robotics-benchmark
A benchmark of sandboxed agentic robotics tasks scored by a hidden grader, rather than a live gripper control server.
- Mechanism-AI
A constraint-driven agent for planar four-bar linkages with MuJoCo simulation, rather than a server driving physical grippers over ROS 2.
Recurring errors it addresses
Error Index entries this tool is built to reduce or work around.
- A ROS 2 audit tool ignores PushRosNamespace in launch files, so it reports topics as disconnected when they are actually connected under /robot.Error Index
- A misspelled or non-Gazebo hardware plugin only logged an error; startup still returned true and the simulation ran without that piece of hardware. The fix makes a failed plugin load fail startup.Error Index
- The ROS 2 driver header promises the arm holds at full stiffness if the command stream stops, but every motion command in the firmware clears the PARK flag first, so a crash or pulled cable leaves the arm sagging on 0.6x kp fail-soft with zero torque feedforward.Error Index
- The header says do not stall the update loop past about 100 ms, then admits a stalled USB link can stall it for 1.2 s, and one dropped ACK blocks the controller for up to 1.7 s, about 17 missed cycles, in fail-soft.Error Index
Sources
Not verified
- Pricing (no price stated on the repository README)
- Real user voices (recent repo activity is the maintainer's own pull request)
- A named individual builder beyond the SCHUNK-SE-Co-KG organization
- A public release (no releases are published)
Last verified November 6, 2026. Listings are informational. The evidence score measures public, verifiable evidence and is not an endorsement or a compatibility claim.