# AliKarami/MikroMCP [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/AliKarami/MikroMCP  
**GitHub Stars:** 83  
**npm Downloads (last month):** 735  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/alikarami-mikromcp

## Description
Manage MikroTik RouterOS devices through AI assistants — interfaces, firewall rules, DHCP, DNS, routes, WireGuard, WiFi, BGP/OSPF, VLANs, and more. 77 tools with dry-run previews, idempotency checks, circuit breakers, RBAC, and rollback-aware change workflows.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mikromcp": {
    "command": "npx",
    "args": ["-y","mikromcp"]
  }
}
```

## Documentation

## What AliKarami/MikroMCP does

AliKarami/MikroMCP turns MikroTik infrastructure into an MCP tool surface for AI assistants and automation workflows. It connects to RouterOS 7.x devices through the RouterOS REST/API and exposes structured operations for reading state, diagnosing problems, and making guarded changes. SwOS and SwOS Lite switches are also supported experimentally through a reverse-engineered HTTP API.

The tool catalog spans system status, interfaces, VLANs, IP addresses, DHCP leases, DNS records, bridges, WiFi clients, firewall and NAT rules, address lists, routing tables, static routes, BGP, OSPF, WireGuard, logs, files, scripts, scheduler jobs, and containers. Diagnostic operations include router-originated ping, traceroute, torch, log filtering, and guarded SSH commands.

## How it works

MCP clients call schema-defined tools rather than sending improvised RouterOS shell commands. Results can include both operator-readable text and structured JSON, allowing an assistant to summarize findings or chain several operations into a larger investigation.

Read operations support retry behavior, while each router has a circuit breaker to limit repeated failures. Changes can be previewed with dry runs and organized into a plan/apply/rollback sequence. Idempotent writes, snapshots, a write journal, correlation IDs, structured logs, audit logs, RBAC, router and tool restrictions, maintenance controls, and confirmation tokens provide additional safeguards around mutations.

For single-router deployments, the optional `MIKROMCP_DEFAULT_ROUTER` setting can supply the default router ID. The server also publishes MCP initialization instructions so compatible clients can discover guidance for using its tools.

## Setup and configuration

The quick-start path uses Node.js 22 or newer, installs the package globally, and then initializes it:

```text
npm install -g mikromcp
mikromcp init
```

That flow targets a single-router stdio deployment. MikroMCP also supports standalone binaries, Docker, Streamable HTTP, and legacy SSE for remote or service-style deployments. RouterOS API prerequisites and deployment-specific configuration are part of the setup process, so choose the transport based on whether the client runs locally with the router workflow or connects to a remote service.

MCP clients named for the project include Claude Desktop, Claude Code, Cursor, and Codex. Stdio is intended for desktop-style clients, while Streamable HTTP and SSE support remote connections.

## Tools and capabilities

- Inspect system resources, versions, interfaces, routes, DNS settings, and logs.
- Manage firewall filters, NAT and mangle rules, address lists, routing rules, VLANs, DHCP, and DNS records.
- Examine WireGuard peers, BGP peers, OSPF neighbors, WiFi clients, and interface health.
- Preview, plan, apply, journal, snapshot, and roll back configuration changes.
- Operate SwOS switch ports, PoE, SFP diagnostics, backups, firmware upgrades, and whole-configuration YAML workflows.
- Apply HTTP bearer authentication, bcrypt token hashes, RBAC, confirmation tokens, and router or tool restrictions.

## Limitations and notes

SwOS support is marked experimental and uses a reverse-engineered `.b` HTTP API. Whole-switch writes include a firmware-compatibility check and are guarded rather than treated like ordinary RouterOS operations.

The documented platform target is RouterOS 7.x, with Node.js 22 or newer for the Node-based installation. SSH is used for operations such as ping and guarded command execution where REST cannot provide the required access; the primary RouterOS integration is through REST/API calls.

_Full upstream README: https://allmcps.com/mcp/alikarami-mikromcp/readme_