robot-motion-mcp
Related Servers
Alternatives to robot-motion-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceThis MCP server enables inspecting ROS 2 manipulators, computing kinematics, planning motion, and managing primitive MoveIt planning-scene objects via a typed API, with no physical execution support.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to work with a local planning workspace, including plans, tasks, examples, approvals, and agent execution state.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to run bounded robotics tasks, retrieve independently verified results, and reuse checked data or artifacts from the local WorldFuzz platform.MIT
- AlicenseCqualityBmaintenanceEnables MCP clients to inspect operational status and channels, lint human-reviewed plans, search and query ledger data, and run queue-based writes with dry-run defaults and safeguards against unverified or unapproved campaigns.472MIT
- AlicenseAqualityBmaintenanceA read-only MCP server that lets an AI agent inspect a ROS2 graph, its underlying DDS participants, readers, writers and QoS mismatches, and recorded bag files, with twelve typed tools that behave the same against a live robot or built-in mock fixtures. It has no write path at all, so it can never publish to the bus or command a robot.18339 PyPI3MIT
- AlicenseNot gradedqualityBmaintenanceEnables clients to inspect workspace status, run bounded planner-coder-reviewer tasks with host-enforced verification, and execute configured checks through three MCP tools.80 npmMIT
TDQS
Scored across 6 tools
Each tool maps to a distinct action/resource: listing tasks, reading task details, reading frozen experiment reports, starting a planning run, polling run status, and validating a run's path. The frozen-report versus live-run-status split is clearly described and unlikely to be confused.
All tools use snake_case with a clear verb_noun pattern: list_tasks, get_task_info, get_experiment_report, start_motion_plan, get_plan_status, validate_motion. The convention is uniform and predictable.
Six tools is well-scoped for a motion-planning server: task inspection, report reading, run initiation, status polling, and validation are each represented exactly once. There is no redundant or filler tool.
The core lifecycle is covered: discover tasks, inspect them, start a plan, poll status, and validate results. Minor gaps remain, such as canceling/stopping an in-flight planning run or listing available runs/reports directly.