io.github.jeff-nasseri/mikrotik-mcp
by halid9
README.md
# MikroTik MCP
<!-- mcp-name: io.github.jeff-nasseri/mikrotik-mcp -->
[](https://mseep.ai/app/jeff-nasseri-mikrotik-mcp)
[](https://www.mikrotik-mcp.com/)
[](https://github.com/jeff-nasseri/mikrotik-mcp/actions/workflows/publish.yml)
[](https://github.com/jeff-nasseri/mikrotik-mcp/actions/workflows/publish.yml)
[](https://github.com/jeff-nasseri/mikrotik-mcp/blob/master/LICENSE)
## Overview
MikroTik MCP provides a bridge between AI assistants and MikroTik RouterOS devices. It allows AI assistants to interact with MikroTik routers through natural language requests, executing commands like managing VLANs, configuring firewall rules, handling DNS settings, and more.
With ~300 tools, it covers practically the whole RouterOS surface: system core (identity, clock, NTP, packages/upgrade, scripts, scheduler, logging), L2 switching (bridge + VLAN filtering, bonding, VRRP, VXLAN), tunnels and VPN (EoIP/GRE/IPIP/6to4, PPP/PPPoE/L2TP/SSTP/OVPN, IPsec, WireGuard), the full firewall (filter/NAT/mangle/raw/address-list/connection), IPv4 and IPv6 (addresses, routes, DHCP client/server/leases, IPv6 firewall), routing protocols (OSPF, BGP, RIP, BFD), certificates (incl. ACME), ROS7 WiFi + legacy CAPsMAN, LTE, containers, and diagnostics (ping, traceroute, bandwidth-test, torch, sniffer, netwatch).
### Tool design
- **Legacy scopes** (the original ~170 tools) use one tool per action: `create_vlan_interface`, `list_vlan_interfaces`, `remove_vlan_interface`, ā¦
- **Consolidated scopes** (newer tools) use one tool per RouterOS menu with an `action` parameter, e.g. `bridge_port(action="add", ā¦)` / `action="list"` / `action="remove"`. This keeps the tool count manageable while covering every verb.
- Most consolidated tools take an `attributes` dict ā an escape hatch to pass any RouterOS property (kebab-case) not exposed as a typed parameter.
- **`execute_command`** runs a raw RouterOS CLI command ā the fallback for anything not covered by a dedicated tool. Safe mode, when enabled, still applies.
Tools carry MCP risk annotations (read-only / write / destructive / dangerous) so clients can gate confirmations appropriately.
## Demo Videos
### Claude Desktop
https://github.com/user-attachments/assets/24fadcdc-c6a8-48ed-90ac-74baf8f94b59
### Inspector
https://github.com/user-attachments/assets/e0301ff2-8144-4503-83d0-48589d95027d
## Documentation
š **[Full Documentation](docs/README.md)** - Complete guides, API reference, and examples
> š **Prefer to read online?** The same documentation is also published at **[www.mikrotik-mcp.com](https://www.mikrotik-mcp.com/)** ([docs](https://www.mikrotik-mcp.com/docs/)) ā an optional, web-friendly way to explore the project while reviewing the repo.
### Quick Links
- **[Installation Guide](docs/getting-started/installation.md)** - Get started with MikroTik MCP
- **[Testing Guide](docs/getting-started/testing.md)** - Run integration tests
- **[Claude Desktop Integration](docs/integrations/claude-desktop.md)** - Configure for Claude Desktop
- **[MCP Inspector](docs/integrations/inspector.md)** - Interactive testing tool
- **[Contributing Guide](docs/contributing.md)** - Help improve MikroTik MCP
- **[Articles](docs/articles/README.md)** - Learning resources and tutorials
## License
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
This server cannot be deployed
Maintenance
ActivitySlowing
ResponsivenessNo issues