MikroTik RouterOS MCP Server

MikroTik RouterOS is an MCP integration. MikroTik RouterOS over the binary API, addressing rules by real .id not list position.

Packages and local setup

The published pypi package is mikrotik-mcp, version 0.3.0. Its declared MCP transport is stdio.

The package declares MIKROTIK_HOST (required): IP address or hostname of the router, e.g. 192.168.88.1; MIKROTIK_USERNAME (required): RouterOS user. Use a dedicated account rather than admin; its group must carry the api policy, and a group without it is rejected with the same error as a wrong password.; MIKROTIK_PASSWORD (required): Password for that user.; MIKROTIK_PORT: API port: 8729 for api-ssl (default), 8728 for plaintext.; MIKROTIK_TLS: Use the TLS API. Defaults to true; turning it off sends the router password over the network in the clear.; MIKROTIK_TLS_FINGERPRINT: SHA-256 of the router certificate. MikroTik's API-SSL certificate is self-signed, so pinning this is what makes the connection authenticated rather than merely encrypted.; MIKROTIK_TIMEOUT: Connection timeout in seconds. Defaults to 10..

Before connecting

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.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.3.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 other integrations MCP servers for tools that cover the same kind of work.