Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
uvx mikrotik-rest-mcp-server==0.1.2Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
MIKROTIK_BASE=<value> MIKROTIK_USERNAME=<value> MIKROTIK_PASSWORD=<secret> MIKROTIK_PASSWORD_FILE=<value> MIKROTIK_MODE=<value> claude mcp add io.github.sogl-mikrotik-rest-mcp -- uvx mikrotik-rest-mcp-server==0.1.2Run in a terminal.
{ "mcpServers": { "io.github.sogl-mikrotik-rest-mcp": { "command": "uvx", "args": [ "mikrotik-rest-mcp-server==0.1.2" ], "env": { "MIKROTIK_BASE": "<value>", "MIKROTIK_USERNAME": "<value>", "MIKROTIK_PASSWORD": "<secret>", "MIKROTIK_PASSWORD_FILE": "<value>", "MIKROTIK_MODE": "<value>" } } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
English | Русский
MCP server that gives coding agents structured access to a RouterOS 7 device over its REST API — reads, filtered queries, guarded writes, a scheduled rollback guard, container shell, and file transfer. One MCP server over stdio.
Built for real ops work: the agent can inventory the router, diff firewall/routing state, poke containers, watch counters, and apply changes — with a human confirmation gate in front of anything disruptive.
MikroTik RouterOS 7 REST MCP: filtered reads, guarded writes, timed rollback
get_* tools for the common collections (firewall, routes, DHCP, DNS, interfaces, WireGuard, containers, scheduler, logs, system resources).get_* endpoints stay callable by name through the same filter pipeline — they are deliberately unlisted so the tool schema stays small. catalog_search makes them discoverable.routeros_get takes any /rest/ path directly, plus routeros_batch for up to 16 parallel reads in one call.where filters with __contains, __in, __not, __gt, __gte, __lt, __lte, __startswith, __endswith.fields projection, sort_by, limit, compact (one-line-per-item output that saves a lot of tokens)..proplist / .query pass-through for server-side filtering.MIKROTIK_MODE=readonly: mutation/execution tools are not registered at all — the protocol surface itself is read-only, not just policy-gated.MIKROTIK_MODE=careful (default): operations classified as disruptive return requires_confirmation — the agent relays it to the user and re-runs with confirm: true after approval. MCP elicitation shows a native dialog where supported. The confirmation flag is a UX gate, not a security boundary — the RouterOS account permissions are what actually limits the agent.PUT only on known collections, PATCH/DELETE only on collection/<id> items, POST only on an explicit action allowlist (ping, traceroute, fetch, file/read, script/run, dns flush, backup/save, export, container shell — see catalog.py).MIKROTIK_STRICT_CONFIRM=1 gates every mutation.MIKROTIK_MODE=yolo removes all gates and can switch to a separate full-privilege account (MIKROTIK_YOLO_USERNAME / MIKROTIK_YOLO_PASSWORD_FILE) — for supervised automation windows only.apply_safe snapshots the target, arms an on-router scheduler, then applies the mutation. Once armed, the rollback no longer depends on the MCP process or client staying alive — commit_safe disarms it within window_seconds.PATCH (restores the snapshotted values of changed fields — not transactional, no concurrent-edit detection) and DELETE (best-effort recreate; list position and generated fields are not preserved — the response says so). PUT is rejected because a created item's .id can't be known until after it exists.commit_safe keeps the pending record if disarm fails so it can be retried.safe_status reports currently armed rollbacks.container_shell runs commands inside RouterOS containers by name or .id — off by default (MIKROTIK_ENABLE_CONTAINER_SHELL), confirmation-gated in careful mode, and the generic routeros_write path can't bypass the flag. timeout_seconds overrides the REST timeout for long-running commands.container_apply_safe / container_commit_safe — transactional shell commands inside containers: snapshots snapshot_paths, runs the mutation, check_cmd rolls back immediately on failure, and a repeating RouterOS-scheduler watchdog restores the snapshot unless committed in time. One active transaction per container.interface_traffic measures live rx/tx bps and pps over a sampling window; routeros_watch diffs numeric fields across samples — counter deltas without two manual reads.run_ping, run_traceroute, run_fetch, run_wifi_monitor, describe_path (field introspection before you write filters).download_file / upload_file.MIKROTIK_ENABLE_LOCAL_FILES + MIKROTIK_LOCAL_ROOT confine it to one directory; transfers are capped at 8 MiB and download_file requires overwrite: true to replace an existing local file.MIKROTIK_PASSWORD_FILE (recommended) or MIKROTIK_PASSWORD.password/secret/psk/token/private-key-shaped fields (MIKROTIK_REDACT=0 disables). Redaction is field-name based — secrets embedded in free-form text (comments, script bodies, log lines, file contents) are not reliably detected.readOnlyHint, destructiveHint, idempotentHint, openWorldHint) on every tool so clients can enforce their own policy.www-ssl recommended; plain HTTP via www requires RouterOS 7.9+ and should be used only on isolated networks — REST uses Basic auth, readable on the wire.read + api + rest-api for read-only use. Add write + test for mutations/diagnostics, ftp for file tools (download_file, /file/read). Script entries have their own policy attribute — the account only needs write to run them, and cannot run a script with broader policy than it possesses.pipx install mikrotik-rest-mcp-server # or: uvx mikrotik-rest-mcp-server
This exposes the mikrotik-rest-mcp-server console script. For development: git clone + pip install -e .
Point your MCP client at the server:
{
"mcpServers": {
"mikrotik_rest": {
"command": "mikrotik-rest-mcp-server",
"env": {
"MIKROTIK_BASE": "https://192.168.88.1",
"MIKROTIK_USERNAME": "mcp-agent",
"MIKROTIK_PASSWORD_FILE": "/path/to/password-file"
}
}
}
}
See .env.example for the full variable list (modes, capability flags, timeouts, TLS verification).
# ops account — reads, config writes, diagnostics; no user/policy management,
# no sensitive fields, no reboot
/user group add name=agent policy=read,write,api,rest-api,test,ftp
/user add name=mcp-agent group=agent password=<random>
# monitoring-only account (pair with MIKROTIK_MODE=readonly)
/user group add name=monitor policy=read,api,rest-api,test
For yolo mode, create a second account in full and wire it via MIKROTIK_YOLO_*. Omit ftp if you don't need file tools.
Typical flow an agent follows:
get_dhcp_leases {compact: true} → quick device list
routeros_batch {requests: [...]} → status in one call
describe_path {path: "/rest/interface/ethernet"} → field names before filtering
interface_traffic {name: "ether1", seconds: 2} → live throughput
routeros_watch {path: ..., diff: true} → counter deltas
routeros_write {method: "PATCH", ...} → routine config edit
routeros_write {method: "DELETE", ...} → stops for confirmation
apply_safe {method: "PATCH", path: "…/<.id>", window_seconds: 60}
→ rollback armed on router; commit_safe to keep
run_script_inline creates a temporary RouterOS script, runs it, and removes it (always confirmed in careful mode). container_shell and host file transfer need their opt-in flags.
src/mikrotik_rest_mcp/
client.py — REST transport, TLS, env config
catalog.py — endpoint/tool tables (pure data)
policy.py — risk tiers, confirmation gate, mutation allowlist
output.py — secret redaction, filters, compact serialization
files.py — local file sandbox + router file helpers
safe_apply.py — snapshot/rollback machinery
server.py — tool list, dispatch, resources, entrypoint
pytest tests/
Unit tests run without a router (REST calls are mocked).
See SECURITY.md. Don't point this at routers you don't administer; treat yolo as a loaded gun and container_shell as remote code execution (because it is).
© 2026 MCP Directory.
MikroTik RouterOS 7 REST MCP: filtered reads, guarded writes, timed rollback
{ "mcpServers": { "io.github.sogl-mikrotik-rest-mcp": { "command": "uvx", "args": [ "mikrotik-rest-mcp-server==0.1.2" ], "env": { "MIKROTIK_BASE": "<value>", "MIKROTIK_USERNAME": "<value>", "MIKROTIK_PASSWORD": "<secret>", "MIKROTIK_PASSWORD_FILE": "<value>", "MIKROTIK_MODE": "<value>" } } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: MIKROTIK_BASE, MIKROTIK_USERNAME, MIKROTIK_PASSWORD, MIKROTIK_PASSWORD_FILE, MIKROTIK_MODE.
Mikrotik Rest runs locally over stdio.
Last checked 2026-11-09. MikroTik RouterOS 7 REST MCP: filtered reads, guarded writes, timed rollback