Mikrotik MCP

What mikrotik-mcp does

mikrotik-mcp MCP server provides an MCP bridge between AI assistants and MikroTik RouterOS devices. Requests written in natural language can be translated into commands for network administration tasks. The documented scope includes VLAN management, firewall configuration, NAT, routing, DHCP, DNS, and WireGuard, along with other RouterOS operations.

The project is intended for environments where an assistant needs to work with MikroTik equipment rather than only provide general networking advice. It can interact with individual devices and, from version 0.14.0 onward, supports managing multiple MikroTik devices through an inventory structure.

How it works

mikrotik-mcp MCP server communicates with MikroTik routers through SSH. An MCP-compatible assistant sends a request to the server, which uses the router connection to execute the corresponding RouterOS commands. The result is then available to the assistant for reporting or continued work.

The repository demonstrates integrations with Claude Desktop and the MCP Inspector. Its documentation also includes architecture diagrams, testing guidance, API reference material, and examples. The inventory feature provides a way to organize a fleet of MikroTik devices so an AI assistant can address devices within that managed set.

Because the server can execute configuration commands, it should be used with credentials and network access appropriate for the routers being managed. The supplied material does not describe an approval workflow or a separate read-only mode.

Tools and capabilities

mikrotik-mcp MCP server covers the following documented administration areas:

• Manage VLAN configuration.
• Configure and inspect firewall rules.
• Work with NAT settings.
• Handle routing configuration.
• Manage DHCP settings.
• Configure DNS settings.
• Work with WireGuard configuration.
• Address multiple devices through the inventory feature introduced in version 0.14.0.

The README describes these as examples of the server’s RouterOS interactions rather than a complete tool-by-tool API list. Consult the project’s full API reference for the exact available operations and request formats.

Setup and configuration

The repository includes an installation guide, a testing guide, and a dedicated Claude Desktop integration guide. It also links to instructions for using the MCP Inspector for interactive testing. The provided material does not specify package commands, configuration-file syntax, required environment variables, or the exact SSH credential fields, so those details should be taken from the project documentation before deployment.

The server is licensed under MIT. The README also links to online documentation at mikrotik-mcp.com, including the project’s getting-started and integration material.

Limitations and notes

The supplied README does not provide a complete list of MCP tool names, supported RouterOS versions, authentication options, or transport details. It confirms SSH-based router interaction and the listed networking domains, but does not establish compatibility with every MCP client. Claude Desktop is explicitly documented; other client support should be verified against the integration documentation.