What it does
MikroMCP is a Model Context Protocol server for MikroTik RouterOS routers and SwOS switches. Its tools cover system status, interfaces, VLANs, IP addresses, DHCP, DNS records, firewall and NAT rules, routing tables, BGP and OSPF visibility, and diagnostics such as ping, traceroute and torch. Write operations support dry-run previews, idempotent changes, snapshots and rollback.
It suits AI assistants such as Claude Code, Claude Desktop, Cursor and Codex that need to inspect or troubleshoot MikroTik equipment in natural language, or to plan and apply configuration changes with a preview and a way to revert them. Access control includes bearer authentication, bcrypt-hashed tokens, RBAC, router and tool restrictions and confirmation tokens, with audit logs kept for actions.
It runs over stdio for a single router, or over Streamable HTTP and legacy SSE for remote clients. Standalone binaries and Docker are also covered in the Getting Started guide. Single-router setups can omit the routerId parameter by setting a default router.
Limitations and requirements
SwOS support is marked experimental and relies on a reverse-engineered HTTP API. Setup requires the RouterOS API prerequisites described in the Getting Started guide. SSH is used for ping and for guarded command execution where the REST API cannot reach.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
MikroMCP
MCP server for MikroTik RouterOS and SwOS: typed tools, dry-run, RBAC, audit logs, and rollback.
v1.16.1As shown on registry.modelcontextprotocol.io when we last read it