MCP server for MikroTik routers: firewall, NAT, routing, DHCP, DNS, WireGuard and more via SSH.
Mikrotik-mcp is an MCP integration. MCP server for MikroTik routers: firewall, NAT, routing, DHCP, DNS, WireGuard and more via SSH.
The published pypi package is mcp-server-mikrotik, version 0.24.2.0. Its declared MCP transport is stdio.
The package declares MIKROTIK_HOST: IP address or hostname of the MikroTik router (single-device mode; default: 127.0.0.1). Not needed when an inventory is configured.; MIKROTIK_USERNAME: SSH username for the MikroTik router (single-device mode; default: admin); MIKROTIK_PASSWORD: SSH password for the MikroTik router (single-device mode); MIKROTIK_PORT: SSH port of the MikroTik router (single-device mode; default: 22); MIKROTIK_KEY_FILENAME: Path to SSH private key file for key-based authentication (single-device mode); MIKROTIK_READ_ONLY: When true, expose only tools that do not modify RouterOS or its file store. Use a read-only RouterOS account as defence in depth.; MIKROTIK_SENSITIVE_HIDING: When true, redact recognized credentials and private key material from tool results, MCP notifications, and logs, and omit tools that return opaque sensitive payloads.; MIKROTIK_INVENTORY_FILE: Path to a YAML file listing multiple MikroTik devices (title, host, port, username, password, key_filename, tags, region). See docs/reference/inventory.; MIKROTIK_INVENTORY: Inline multi-device inventory as a YAML (or JSON) list; takes precedence over MIKROTIK_INVENTORY_FILE and the single-device variables. Holds credentials..
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 0.24.2.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related developer tools MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| MIKROTIK_HOST | IP address or hostname of the MikroTik router (single-device mode; default: 127.0.0.1). Not needed when an inventory is configured. | Check documentation |
| MIKROTIK_USERNAME | SSH username for the MikroTik router (single-device mode; default: admin) | Check documentation |
| MIKROTIK_PASSWORD | SSH password for the MikroTik router (single-device mode) | Check documentation |
| MIKROTIK_PORT | SSH port of the MikroTik router (single-device mode; default: 22) | Check documentation |
| MIKROTIK_KEY_FILENAME | Path to SSH private key file for key-based authentication (single-device mode) | Check documentation |
| MIKROTIK_READ_ONLY | When true, expose only tools that do not modify RouterOS or its file store. Use a read-only RouterOS account as defence in depth. | Check documentation |
| MIKROTIK_SENSITIVE_HIDING | When true, redact recognized credentials and private key material from tool results, MCP notifications, and logs, and omit tools that return opaque sensitive payloads. | Check documentation |
| MIKROTIK_INVENTORY_FILE | Path to a YAML file listing multiple MikroTik devices (title, host, port, username, password, key_filename, tags, region). See docs/reference/inventory. | Check documentation |
| MIKROTIK_INVENTORY | Inline multi-device inventory as a YAML (or JSON) list; takes precedence over MIKROTIK_INVENTORY_FILE and the single-device variables. Holds credentials. | Check documentation |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.