ROS-MCP

ROS-MCP is a small MCP gateway for managing multiple MikroTik RouterOS devices over SSH. It exposes exactly two tools and keeps device credentials, SSH session reuse, retries, timeouts, and output limits behind the gateway.

Despite the project name, ROS means MikroTik RouterOS, not Robot Operating System.

MCP tools

device_list

Returns the configured, non-sensitive device inventory. It performs no network I/O and never returns passwords, private keys, environment-variable names, or host-key fingerprints.

command_execute

command_execute(device: string, command: string, dry_run: boolean = true)

• device is always required. There is no implicit default-device fallback.

• command is one RouterOS CLI line, limited to 8 KiB.

• dry_run=true validates locally and does not open an SSH connection.

• A result with status=unknown means the command may have executed and must not be retried automatically.

The gateway does not implement RouterOS Safe Mode and does not claim that a dry run validates RouterOS syntax or effects.

Related MCP server: SSH MCP Server

Configuration

ROS_DEVICES_JSON is required and must be a JSON object keyed by device ID. Each device references its own credential environment variable.

{
  "main": {
    "display_name": "Main Router",
    "description": "Internet edge",
    "host": "192.168.88.1",
    "port": 22,
    "username": "ai-mgmt",
    "enabled": true,
    "tags": ["production", "edge"],
    "connect_timeout_seconds": 15,
    "command_timeout_seconds": 25,
    "keepalive_seconds": 30,
    "idle_ttl_seconds": 300,
    "output_limit_bytes": 1048576,
    "auth": {
      "type": "password",
      "password_env": "ROS_MAIN_PASSWORD"
    },
    "host_key": {
      "fingerprint_sha256": "SHA256:REPLACE_WITH_43_BASE64_CHARACTERS"
    }
  },
  "office": {
    "display_name": "Office Router",
    "host": "10.0.0.1",
    "port": 22,
    "username": "ai-mgmt",
    "auth": {
      "type": "private_key",
      "private_key_env": "ROS_OFFICE_PRIVATE_KEY",
      "passphrase_env": "ROS_OFFICE_KEY_PASSPHRASE"
    },
    "host_key": {
      "fingerprint_sha256": "SHA256:REPLACE_WITH_43_BASE64_CHARACTERS"
    }
  }
}

Set the referenced secrets separately:

ROS_MAIN_PASSWORD=<main RouterOS SSH password>
ROS_OFFICE_PRIVATE_KEY=<complete PEM/OpenSSH private-key text>
ROS_OFFICE_KEY_PASSPHRASE=<optional key passphrase>

Device IDs must match ^[a-z][a-z0-9_-]{0,63}$. Configuration is validated and resolved once at startup. Missing secrets, unknown fields, duplicate JSON keys, invalid IDs, and malformed SHA-256 fingerprints prevent startup.

The host-key fingerprint is mandatory. Unknown keys are never accepted through TOFU or Paramiko's AutoAddPolicy.

Run locally

Python 3.11 or newer and uv are required for local development.

uv sync --all-groups
export ROS_DEVICES_JSON='{"main":{"host":"192.168.88.1","username":"ai-mgmt","auth":{"type":"password","password_env":"ROS_MAIN_PASSWORD"},"host_key":{"fingerprint_sha256":"SHA256:REPLACE_WITH_43_BASE64_CHARACTERS"}}}'
export ROS_MAIN_PASSWORD='replace-me'
uv run ros-mcp

The process speaks MCP over stdio. Application code does not write ordinary messages to stdout because stdout belongs to the protocol.

Docker

Published images are available from GHCR:

docker pull ghcr.io/asharca/ros-mcp:latest

main publishes latest, main, and sha-<commit> tags. Git tags such as v1.2.3 additionally publish 1.2.3 and 1.2.

To build locally:

docker build -t ros-mcp:local .
docker run --rm -i \
  --read-only \
  --tmpfs /tmp:rw,size=16m \
  -e ROS_DEVICES_JSON \
  -e ROS_MAIN_PASSWORD \
  ros-mcp:local

The image runs as a non-root user, exposes no port, and starts the stdio MCP server directly. Its root filesystem is safe to run read-only.

ToolPlane

1. Publish the image to a registry reachable by ToolPlane's Docker daemon.

2. In a workspace, choose MCP > Add custom MCP > Docker.

3. Enter the image reference and leave Start Command empty.

4. Add ROS_DEVICES_JSON and all referenced secret variables on the deployment's Variables page, then restart it.

5. Leave Disconnect from network disabled so the container can reach RouterOS SSH addresses.

ToolPlane currently has a 30-second call timeout. Configure command_timeout_seconds to about 25 seconds there, or raise ToolPlane's timeout above the gateway's command timeout.

Execution behavior

• One reusable SSH session is maintained per device.

• Commands for the same device are serialized in a bounded FIFO.

• Different devices can execute concurrently.

• A stale session may reconnect once before command dispatch.

• A command is never replayed after dispatch.

• stdout and stderr are drained concurrently and retained up to the configured per-stream byte limit.

• All SSH clients are explicitly closed during MCP server shutdown.

Logging

ROS-MCP has no audit-log Module, log-query tool, command history, or persistent request/output storage. Expected operational failures are returned as structured tool results. The MCP runtime is configured to emit only error-level diagnostics to stderr.

Development

uv run pytest
uv run ruff check src tests
uv run ruff format --check src tests