Robonine MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROBONINE_MCP_PORT | No | WebSocket port the browser tab connects to | 60808 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_connectionA | Check whether the browser relay (Robonine web app with MCP Bridge plugin) is connected. Returns "connected" or "not connected". |
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 1 tool
With only one tool, there is no possibility of ambiguity or confusion between tools.
The single tool name 'check_connection' follows a clear verb_noun pattern, consistent by default.
The server offers only one trivial tool, which is extremely insufficient for any substantive functionality or scope implied by the server name.
The server provides no meaningful operations beyond a connectivity check, leaving all other possible actions completely uncovered.