Robotics MCP Server
# Robotics MCP Server
<p align="center">
<a href="https://github.com/casey/just"><img src="https://img.shields.io/badge/just-ready_to_go-7c5cfc?style=flat-square&logo=just&logoColor=white" alt="Just"></a>
<a href="https://github.com/astral-sh/ruff"><img src="https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json" alt="Ruff"></a>
<a href="https://python.org"><img src="https://img.shields.io/badge/Python-3.13+-3776AB?style=flat-square&logo=python&logoColor=white" alt="Python"></a>
<a href="https://biomejs.dev"><img src="https://img.shields.io/badge/Linted_with-Biome-60a5fa?style=flat-square&logo=biome&logoColor=white" alt="Biome"></a>
<a href="https://github.com/PrefectHQ/fastmcp"><img src="https://img.shields.io/badge/FastMCP-3.4.4+-7c5cfc?style=flat-square" alt="FastMCP"></a>
</p>
> 📖 **[Installation Guide](INSTALL.md)** — quick start, manual setup, and troubleshooting
**Author:** FlowEngineer sandraschi
One MCP server for physical robots (Dreame vacuums, Yahboom ROS, Elegoo, Nori A3), Gazebo, and virtual stacks (Unity, VRChat). FastMCP, **stdio** + **HTTP**. Optional **watchfiles** restarts for dev or unattended runs (not an SLA).
| Doc | Contents |
|-----|----------|
| **[Technical README](docs/README_TECHNICAL.md)** | Prerequisites, hardware, install, packaging, Cursor, config, composed MCPs, testing, troubleshooting |
| **[Usage and API](docs/README_USAGE.md)** | Tool examples, web UI, HTTP endpoints |
| **[Android Doctrine](docs/doctrine/README.md)** | Safety, legal, and operational standards for the android fleet |
| **[Setup Prerequisites](docs/guides/SETUP_PREREQUISITES.md)** | Unity, VRChat, peer MCP servers when you need the full stack |
| **[Crash protection (watchfiles)](WATCHFILES_README.md)** | Auto-restart and health checks |
**Status:** Industrial **v1.4.1** (2026-04-14) | SOTA v1.4.1 Compliance | Benny Protocol Secured.
[](https://github.com/FlowEngineer/sota)
[]()
[](https://github.com/jlowin/fastmcp)
[](https://biomejs.dev)
[](https://www.python.org)
[](LICENSE)
## Quick Start
```powershell
git clone https://github.com/sandraschi/robotics-mcp
cd robotics-mcp
just
```
This opens an interactive dashboard showing all available commands. Run `just bootstrap` to install dependencies, then `just serve` or `just dev` to start.
### Manual Setup
If you don't have `just` installed:
## Install
```bash
uvx robotics-mcp
```
```bash
pip install robotics-mcp
```
Development clone: see [Installation](docs/README_TECHNICAL.md#installation) in the technical README.
## Contributing
See [CONTRIBUTING.md](CONTRIBUTING.md).
## 🛡️ Industrial Quality Stack
This project adheres to **SOTA 14.1** industrial standards for high-fidelity agentic orchestration:
- **Python (Core)**: [Ruff](https://astral.sh/ruff) for linting and formatting. Zero-tolerance for `print` statements in core handlers (`T201`).
- **Webapp (UI)**: [Biome](https://biomejs.dev/) for sub-millisecond linting. Strict `noConsoleLog` enforcement.
- **Protocol Compliance**: Hardened `stdout/stderr` isolation to ensure crash-resistant JSON-RPC communication.
- **Automation**: [Justfile](./justfile) recipes for all fleet operations (`just lint`, `just fix`, `just dev`).
- **Security**: Automated audits via `bandit` and `safety`.
## License
MIT see [LICENSE](LICENSE).
## Acknowledgments
FastMCP; ROS community; Unity3D, VRChat, World Labs Marble/Chisel; MCP ecosystem contributors.
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.