mikrotik-mcp

Package (pypi 0.24.2.0)

uvx mcp-server-mikrotik

Or add to your MCP client config:

{
  "mcpServers": {
    "mikrotik-mcp": {
      "command": "uvx",
      "args": [
        "mcp-server-mikrotik"
      ],
      "env": {
        "MIKROTIK_HOST": "<YOUR_VALUE>",
        "MIKROTIK_USERNAME": "<YOUR_VALUE>",
        "MIKROTIK_PASSWORD": "<YOUR_VALUE>",
        "MIKROTIK_PORT": "<YOUR_VALUE>",
        "MIKROTIK_KEY_FILENAME": "<YOUR_VALUE>",
        "MIKROTIK_READ_ONLY": "<YOUR_VALUE>",
        "MIKROTIK_SENSITIVE_HIDING": "<YOUR_VALUE>",
        "MIKROTIK_INVENTORY_FILE": "<YOUR_VALUE>",
        "MIKROTIK_INVENTORY": "<YOUR_VALUE>"
      }
    }
  }
}

• 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 secret — 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 secret — Inline multi-device inventory as a YAML (or JSON) list; takes precedence over MIKROTIK_INVENTORY_FILE and the single-device variables. Holds credentials.