Robonine MCP Server
Officialby roboninecom
README.md
# Robonine MCP Server
A local MCP server that connects Claude Code (or any MCP-compatible AI assistant) to a Robonine robot arm. The server runs on your machine and relays tool calls to the Robonine web app open in your browser — no robot data passes through any remote server.
## How it works
```
Claude Code ←stdio→ MCP server ←ws://127.0.0.1:60808→ Browser tab → BT/USB → Robot
```
The MCP server starts a WebSocket server on `127.0.0.1:60808`. The Robonine web app connects to it automatically when the MCP Bridge plugin is installed and active. Once connected, Claude Code can read robot state and send motion commands.
## Installation
### From GitHub
Claude Code fetches and runs the server automatically — no manual steps needed:
```bash
claude mcp add robonine -- npx -y github:roboninecom/robonine-mcp
```
Or add to your MCP host config:
```json
{
"mcpServers": {
"robonine": {
"command": "npx",
"args": ["-y", "github:roboninecom/robonine-mcp"]
}
}
}
```
### Local (from this repo)
Build once, then point Claude Code at the compiled file:
```bash
cd mcp && npm install && npm run build
claude mcp add robonine -- node /path/to/student-lab/mcp/dist/index.js
```
## Setup in the browser
1. Open [lab.robonine.com](https://lab.robonine.com) (or your local dev instance).
2. Install the **MCP Bridge** plugin from the plugin marketplace.
3. Connect your robot arm.
4. The browser tab connects to the local MCP server automatically — the MCP Bridge plugin page shows the relay status.
## Available tools
| Tool | Description |
|---|---|
| `robot_list` | List currently connected robot arms |
| `robot_get_position` | Get joint angles and end-effector position |
| `robot_set_joints` | Move the arm to specified joint positions |
| `robot_stop` | Disable torque on all servos |
| `user_robot_list` | List your registered robots |
| `path_list` | List your saved motion paths |
| `path_read` | Read a motion path with all waypoints |
## Configuration
| Env var | Default | Description |
|---|---|---|
| `ROBONINE_MCP_PORT` | `60808` | WebSocket port the browser tab connects to |
If you change the port, set the same value in the MCP Bridge plugin settings.
TDQS
A3.8/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or confusion between tools.
Naming Consistency5/5
The single tool name 'check_connection' follows a clear verb_noun pattern, consistent by default.
Tool Count1/5
The server offers only one trivial tool, which is extremely insufficient for any substantive functionality or scope implied by the server name.
Completeness1/5
The server provides no meaningful operations beyond a connectivity check, leaving all other possible actions completely uncovered.
Maintenance
ActivityInactive
ResponsivenessNo issues