ROS-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROS_DEVICES_JSON | Yes | A JSON object keyed by device ID. Each device includes host, username, auth settings, and host_key. Referenced secrets (e.g., password_env, private_key_env, passphrase_env) must be set as separate environment variables. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| device_listA | List configured RouterOS devices without connecting to them or exposing credentials. |
| command_executeA | Execute a command on one device. Commands may be non-idempotent. When the result reports an unknown outcome, the command may already have run and must not be retried automatically. |
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 2 tools
The two tools have completely distinct purposes: device_list is a read-only discovery operation and command_execute performs actions on a device. There is no realistic way to confuse them.
Both names follow a clean, consistent noun_verb pattern (device_list, command_execute). The convention is uniform across the entire surface.
Two tools is on the thin side for a RouterOS management server, even though a generic command gateway offsets some of that. It sits at the borderline the rubric flags as 1-2 tools feeling sparse.
The generic command_execute provides broad coverage of RouterOS operations, but there is no way to add, remove, or configure a device despite device_list referencing 'configured' devices, leaving a lifecycle gap.