Robotics MCP Server

Robotics MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Robotics Control MCP server. Tools: list devices, send command, read sensor. Built by MEOK A...

What you get

IoT and robotics interface: list devices, send serial/HTTP commands, read sensors, control servos, send G-code, and emergency stop. Part of MEOK AI Labs' HARVI project.

What the assistant can call

Once Robotics is connected, these are the calls the assistant has available:

• Well — documented API
• Production-ready — Active maintenance
• Pro — ** $99/mo — Full MCP suite + EU AI Act tracking
• Enterprise — ** $499/mo — Custom dev + SLA + Dedicated support
• Domain — Purpose
• Tier — Price

Setting it up

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Robotics's toolset — Well, Production-ready, Pro and 3 more — is a fair guide to whether it matches your workflow. It is maintained by CSOAI-ORG; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the robotics mcp server does with a few real requests.