Robotics MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| robotics_systemB | System management portmanteau for Robotics MCP. PORTMANTEAU PATTERN RATIONALE: Instead of creating 3 separate tools (help, status, list_robots), this tool consolidates related system operations into a single interface. This design:
SUPPORTED OPERATIONS:
|
| robot_controlC | Unified robot control with conversational responses. Provides a single interface for controlling physical robots, virtual robots, and specialized devices with intelligent routing and rich conversational responses. Primary: Dreame D20 Pro vacuum. Also supports Yahboom ROSMASTER, Moorebot Scout, Unitree (when hardware available), and virtual robots in Unity/VRChat. PORTMANTEAU PATTERN RATIONALE: Instead of creating separate tools for each robot type and operation, this tool consolidates all robot control operations into a single interface. This design:
SUPPORTED ROBOT TYPES:
SUPPORTED OPERATIONS:
|
| robot_behaviorA | Robot behavior control portmanteau - Animation, camera, navigation, and manipulation. PORTMANTEAU PATTERN: Consolidates animation, camera, navigation, and manipulation operations into a single unified tool. This reduces tool explosion while maintaining full functionality across all behavior categories. CATEGORIES:
ANIMATION ACTIONS:
CAMERA ACTIONS:
NAVIGATION ACTIONS:
MANIPULATION ACTIONS:
|
| robot_manufacturingB | Manufacturing equipment control with conversational responses. Provides unified control over 3D printers, CNC machines, and laser cutters with rich conversational responses for natural AI interaction. Supports complete manufacturing workflows from file upload to finished product. PORTMANTEAU PATTERN RATIONALE: Instead of creating separate tools for each device type and operation, this tool consolidates manufacturing operations into a single interface. This design:
SUPPORTED OPERATIONS:
|
| robot_virtualB | Virtual robot lifecycle and operations portmanteau. PORTMANTEAU PATTERN: Consolidates virtual robot CRUD operations and virtual robotics operations into a single unified tool. This reduces tool explosion while maintaining full functionality for virtual robot management. CRUD OPERATIONS:
VIRTUAL ROBOT OPERATIONS:
|
| robot_modelB | Robot model management portmanteau for Robotics MCP. PORTMANTEAU PATTERN RATIONALE: Instead of creating 4 separate tools (create, import, export, convert), this tool consolidates related model operations into a single interface. This design:
SUPPORTED OPERATIONS:
|
| vbot_crudA | CRUD operations for virtual robots (vbots). This tool provides complete lifecycle management for virtual robots:
Supported robot types:
|
| workflow_managementC | Comprehensive workflow management operations. OPERATIONS:
|
| drone_controlC | Core drone flight control operations with conversational responses. Provides unified control interface for PX4/ArduPilot drones via MAVLink protocol or direct firmware integration. Supports both autonomous and manual flight modes with rich conversational responses for natural AI interaction. |
| drone_streamingC | Manage drone video streaming and recording with conversational responses. Controls FPV video feeds, RTSP/WebRTC streaming, and onboard recording. Supports multiple protocols for real-time monitoring and data capture with intelligent quality adaptation and conversational status updates. |
| drone_navigationB | Manage drone navigation, waypoints, and geofencing with conversational responses. Handles GPS navigation, waypoint missions, geofence boundaries, and follow-me modes with intelligent path planning and safety-aware navigation. Integrates with PX4/ArduPilot navigation systems and RTK positioning for precise aerial operations. |
| drone_flight_controlC | Manage advanced drone flight control, missions, and parameters with conversational responses. Provides fine-grained control over PX4/ArduPilot flight modes, autonomous mission execution, and drone parameter tuning for advanced flight operations with intelligent mission planning and parameter optimization recommendations. |
| dreame_controlA | Dreame D20 Pro vacuum control with conversational responses. Provides unified interface for Dreame vacuum operations: status, battery, water level, suction, LIDAR map, cleaning programs, zone/spot/room cleaning, and configuration. Operations:
|
| dreame_onboardA | Dreame D20 Pro Plus — DreameHome cloud setup (no local token). This server uses the DreameHome cloud API. Set environment variables and optionally the Tasshack ref clone path. No network discovery or miio token needed. Returns: Setup instructions and env var reference. |
| noetix_infoA | Noetix Bumi humanoid robot — features, specs, and SDK links. Operations: info — return features, specs, GitHub and docs links (default) Returns: success, message, and data (specs, features, github, docs). |
| gazebo_modelsB | Manage Gazebo Fuel simulation models - browse, download, and spawn. Browse, download, and spawn 3000+ free models from Gazebo Fuel (fuel.gazebosim.org) into your Gazebo simulation environment. |
| robotics_sim_artB | Sim-art fleet bridge via gimp-mcp HTTP (Gazebo icons, VRChat, avatar thumbs). Uses HTTP tool calls instead of mounting gimp-mcp stdio (avoids protocol hangs). Operations: gimp_status: Probe gimp-mcp health and list sim-art templates. batch_gazebo_icons: Run gimp_sim_art_tool gazebo_model_icons on input_dir. import_gazebo_models: Batch import thumbnails into models_root (auto_import). batch_vrchat_icons: Run vrchat_icon_batch on input_dir. avatar_thumbnail: Push icon_path to avatar via avatar_manager set_thumbnail. |
| robotics_fab_artA | Fab art fleet bridge via inkscape-mcp HTTP (DXF, laser dots, Gazebo schematics). Operations: inkscape_status: Probe inkscape-mcp and list fab presets. batch_dxf_export: Run inkscape_fab_art batch_dxf_export on input_dir. batch_laser_dots: Generate laser dot SVG batch from preset. gazebo_schematic: SVG to PNG schematic for model documentation. stage_fab_paths: Stage DXF/SVG/PNG outputs for robotics workflows. push_gimp_schematic: Export schematic and push through gimp validation. |
| robotics_agentic_workflowC | Execute a complex, multi-step robotics workflow leveraging MCP sampling. |
| sim_fleet_statusA | Probe all registered simulation MCP backends and report availability. Checks: mujoco-mcp (MuJoCo), gazebo-mcp (Gazebo), isaac-mcp (Isaac Sim), limx-robotics-mcp (LimX). Returns health data, strengths, and ports for each. |
| sim_fleet_routeA | Route a simulation task to the best available backend. Probes all running sim MCPs, picks the optimal one based on task keywords (sensors → Gazebo, rendering → Isaac, locomotion → MuJoCo, TRON 1/Oli → LimX), and returns the backend URL and metadata. The caller then makes the actual API call to that backend. |
| sim_fleet_backendsA | List all registered sim backends and their capabilities (offline registry). |
| sim_marketplace_search_toolA | Search the robot model marketplace for available models. Filters by keyword, tags, sim backend, or robot type. When exact keyword match returns nothing, falls back to a local LLM (Ollama) to suggest the closest catalog entry. Return Format{"success": bool, "message": str, "matches": [{ "id", "name", "type", "tags", "sim_backends", "formats", "joint_count", "actuator_count" }], "total": int, "llm_fallback_used": bool} Examplessim_marketplace_search_tool(query="go2") sim_marketplace_search_tool(tags=["humanoid", "unitree"]) sim_marketplace_search_tool(sim_backend="gazebo") |
| sim_marketplace_info_toolA | Get full metadata for a specific robot model from the marketplace. Returns file paths (MJCF, URDF), compatible sim backends, joint/actuator counts, and source URLs. Return Format{"success": bool, "message": str, "model": {"id": str, "name": str, ...} | None} Examplessim_marketplace_info_tool(model_id="unitree_go2") sim_marketplace_info_tool(model_id="limx_oli_d04") |
| environmental_logistics_handlerC | Handle specialized environmental and substrate logistics. Covers everything from textiles and darkroom film to wildlife search & rescue, autonomous security patrols, pet logistics, pool supervision, human health, and mural painting. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.