mikrotik-mcp MCP Server

An MCP (Model Context Protocol) server for managing fleets of MikroTik RouterOS devices from AI assistants such as Claude.

Local serverstdioApache-2.0

What is the mikrotik-mcp Server?

mikrotik-mcp is an MCP project maintained in the vesact/mikrotik-mcp repository. The maintainer describes its purpose as “An MCP (Model Context Protocol) server for managing fleets of MikroTik RouterOS devices from AI assistants such as Claude”. Read the project documentation for the complete scope.

Local setup

The project provides a local client configuration using node. Follow the repository’s build and installation steps before copying it, and replace example paths with the paths on your own computer.

Configuration values

The example declares KEEPASS_PATH, KEEPASS_PASSWORD. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.

Source

Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

Tool	What it does
Area	Examples
System	identity, clock, health, hardware, packages, license, history, note, certificates, log, files
IP	addresses, ARP, routes, pools, IP settings, IP services
Firewall	filter, NAT, mangle, address lists, connection tracking, RADIUS
Services	NTP, SNMP, reboot/shutdown
Diagnostics	ping, traceroute, bandwidth test, torch, packet sniffer, profile, netwatch, fetch, speed test, WoL, MAC/IP scan, traffic generator

How to install the mikrotik-mcp Server

{
  "mcpServers": {
    "mikrotik": {
      "command": "node",
      "args": [
        "/path/to/mikrotik-mcp/dist/index.js"
      ],
      "env": {
        "KEEPASS_PATH": "/path/to/vault.kdbx",
        "KEEPASS_PASSWORD": "YOUR_KEEPASS_PASSWORD"
      }
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Configuration

Variable	Description	Required
KEEPASS_PATH	Declared in the maintainer’s client configuration.	Check documentation
KEEPASS_PASSWORD	Declared in the maintainer’s client configuration.	Yes