MikroTik MCP
# MikroTik MCP
[](https://mcptoplist.com/server/io.github.jeff-nasseri%2Fmikrotik-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.
## 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
### Inventory
> [!NOTE]
> Since MikroTik MCP version `0.14.0`, the MikroTik MCP will allow you to manage multiple MikroTik devices within your fleet structure. The following video simply shows how to use the inventory of MikroTik devices to let LLMs talk with your MikroTik devices.
https://github.com/user-attachments/assets/185b2c39-8f55-4f26-a74c-2ac459ad38f5
## 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
- **[Diagrams](docs/diagrams/README.md)** - Architecture and design diagrams (draw.io)
## 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.
TDQS
Scored across 174 tools
Most resources follow clear list/get/create/update/remove clusters, but there are overlapping convenience tools (get_logs vs get_logs_by_topic/get_logs_by_severity, get_dns_cache vs get_dns_cache_statistics, add_route vs add_default_route) and legacy/unsupported wireless tools that blur boundaries. Descriptions usually clarify, but an agent must compare multiple near-synonyms.
Core CRUD is consistently snake_case verb_noun, but verbs are mixed across equivalent operations: add_ip_address/add_route/add_user vs create_dhcp_server/create_filter_rule/create_queue_type, and set_dns_servers/set_user_ssh_keys vs update_dns_static/update_user. Safe_mode_status and similar noun-first names also deviate, though the overall style remains readable.
174 tools is an extreme surface for any agent to navigate, especially with many convenience wrappers, legacy unsupported functions, and a duplicate get_queue_tree entry. Even for a broad MikroTik domain, this should be split into focused servers.
DHCP support is create-heavy: create_dhcp_network and create_dhcp_pool have no get/list/update/remove, and create_dhcp_server has no update or enable/disable. Several standard RouterOS areas (bridges, firewall mangle/address-lists, DHCP leases) and modern wireless security profiles are absent, while legacy wireless tools are marked unsupported. These gaps create dead ends for common workflows.