GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
MCP server for MikroTik RouterOS and SwOS: typed tools, dry-run, RBAC, audit logs, and rollback.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
MIKROMCP_CONFIG_PATH, MIKROMCP_STDIO_IDENTITY, MIKROMCP_LOG_LEVELYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"mikromcp": {
"command": "npx",
"args": [
"-y",
"mikromcp"
],
"env": {
"MIKROMCP_CONFIG_PATH": "your-value",
"MIKROMCP_STDIO_IDENTITY": "your-value",
"MIKROMCP_LOG_LEVEL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add mikromcp --env MIKROMCP_CONFIG_PATH=your-value --env MIKROMCP_STDIO_IDENTITY=your-value --env MIKROMCP_LOG_LEVEL=your-value -- npx -y mikromcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mikromcp": {
"command": "npx",
"args": [
"-y",
"mikromcp"
],
"env": {
"MIKROMCP_CONFIG_PATH": "your-value",
"MIKROMCP_STDIO_IDENTITY": "your-value",
"MIKROMCP_LOG_LEVEL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"mikromcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mikromcp"
],
"env": {
"MIKROMCP_CONFIG_PATH": "your-value",
"MIKROMCP_STDIO_IDENTITY": "your-value",
"MIKROMCP_LOG_LEVEL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
MIKROMCP_CONFIG_PATH envMIKROMCP_STDIO_IDENTITY envMIKROMCP_LOG_LEVEL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account AliKarami, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.16.1) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
AI-native network automation for MikroTik RouterOS and SwOS. MikroMCP exposes RouterOS routers and SwOS switches as a typed, auditable Model Context Protocol server so Claude, Cursor, Codex, and other MCP clients can inspect, diagnose, and safely operate MikroTik gear in natural language.
MikroMCP exists because raw router CLI access is the wrong abstraction for AI agents. RouterOS is powerful, but asking an LLM to improvise shell commands against production network gear is risky. MikroMCP gives agents a controlled tool surface: strict schemas, idempotent writes, dry-run previews, per-router circuit breakers, retry policies, RBAC, audit logs, snapshots, and rollback-aware change workflows.
In one sentence: MikroMCP turns MikroTik RouterOS into a production-minded MCP control plane for AI infrastructure, DevOps automation, and modern router management.
That's the whole setup for a single-router stdio deployment. For standalone binaries, Docker, HTTP/SSE mode, the RouterOS API prerequisites, and the full 15-minute walkthrough, see the [Getting Started guide](https://github.com/AliKarami/MikroMCP/wiki/Getting-Started).
| Category | What MikroMCP covers |
|---|---|
| 🧭 Router management | System status, clock, reboot, packages, files, scripts, scheduler jobs, containers |
| 🌐 Network operations | Interfaces, VLANs, IP addresses, DHCP leases, DNS static records, bridge ports, WiFi clients |
| 🔥 Firewall and policy | Filter/NAT rules, mangle rules, address lists, route tables, routing rules |
| 🛰️ Routing visibility | Static routes, routing tables, BGP peers, OSPF neighbors |
| 🔀 SwOS switches | *Experimental.* MikroTik SwOS and SwOS Lite switches (deviceType: "swos") over the reverse-engineered .b HTTP API: port links, PoE, SFP diagnostics, guarded whole-blob writes with a firmware-compatibility check, the whole switch config as one YAML document (export, dry-run, apply), backups and firmware upgrades |
| 🔐 Secure access | HTTP bearer auth, bcrypt token hashes, RBAC, router/tool restrictions, confirmation tokens |
| 🧪 Diagnostics | Router-originated ping, traceroute, torch, log filtering, guarded SSH command execution |
| 🛡️ Change safety | Dry-run, idempotent writes, snapshots, write journal, plan_changes, apply_plan, rollback_change |
| ⚙️ Production behavior | Retries for read tools, per-router circuit breakers, correlation IDs, structured logs, audit logs |
| 🤖 AI-agent fit | Human-readable responses plus structured JSON content for reasoning, chaining, and automation; server advertises an instructions string on MCP initialize so clients self-configure; optional routerId resolved via MIKROMCP_DEFAULT_ROUTER for single-router setups; usage skill for safe, guided tool use in Claude Code |
| 🧩 MCP compatibility | stdio for desktop clients, Streamable HTTP and legacy SSE for remote or service-style clients |
133 typed tools in total — browse the full catalog with parameters, defaults, and copy-paste example prompts in [Available Tools](https://github.com/AliKarami/MikroMCP/wiki/Available-Tools).
Use MikroMCP to inspect core-01. Summarize system resources, RouterOS version,
running interfaces, active routes, DNS settings, and recent warning/error logs. Flag anything that looks operationally risky.
List firewall filter and NAT rules on edge-01. Identify disabled rules,
overlapping port forwards, broad accept rules, and anything without comments. Do not change anything yet.
Dry-run a route on core-01 for 10.20.0.0/16 via 192.168.88.1 in the main table.
Show the exact planned diff and tell me whether an existing route conflicts.
Show WireGuard peers on branch-02. Sort by last handshake age and flag peers
that have not handshaken recently or have no transfer counters.
Check interface health on edge-01, then run ping and traceroute from the router
to 1.1.1.1. If packet loss is present, use torch on the WAN interface for a short traffic snapshot.
Create a change plan that adds a DNS record and a firewall address-list entry
on edge-01. Use dry-run first, explain the plan, then wait for approval before applying anything.
MCP gives LLMs a standard way to call tools. MikroMCP makes RouterOS a high-quality MCP target by turning network operations into well-described, machine-readable, permission-aware actions.
AI assistants can use MikroMCP to:
MikroMCP is an open-source Model Context Protocol (MCP) server that exposes MikroTik RouterOS as 133 typed, auditable tools — letting AI assistants inspect, diagnose, and safely operate routers in natural language instead of improvising CLI commands.
The RouterOS REST/API exposes raw endpoints. MikroMCP wraps them in schema-validated, idempotent, dry-run-able tools with RBAC, audit logging, snapshots, and rollback — the safety layer an LLM needs before it touches production gear.
Instead of brittle SSH scripts that screen-scrape CLI output, MikroMCP returns structured, typed results with confirmation gates and per-router circuit breakers. SSH is used only where REST can't reach — ping and guarded run_command.
MikroMCP speaks MCP over stdio and HTTP/SSE, so Claude Code and Claude Desktop drive RouterOS directly. Pair it with the bundled usage skill for safe, guided workflows.
Codex connects to MikroMCP over the standard MCP protocol — see Connecting to AI Assistants.
Cursor connects to MikroMCP as an MCP server (stdio or HTTP) to inspect and manage MikroTik routers without leaving the editor.
Any MCP-compatible client — OpenClaw included — can use MikroMCP; configure it as a stdio or HTTP MCP server.
Start with Getting Started to install and connect, then use the usage skill and Available Tools to automate RouterOS safely with an AI assistant.
MikroMCP is purpose-built for MikroTik/RouterOS operations with production-grade safety — dry-run, rollback, audit, and RBAC — making it a strong MCP choice for network engineers adopting AI tooling.
The README stays intentionally short. Everything below is documented in depth in the wiki:
| Resource | Use it for |
|---|---|
| Getting Started | Install (npm, binary, Docker), configure, and connect in 15 minutes |
| RouterOS API Setup | Enable the REST API, create a user, TLS and firewall |
| Configuration | Router registry, credentials, all environment variables |
| Running | Run commands, HTTP/SSE transport, troubleshooting |
| Connecting to Claude Desktop | Register MikroMCP in Claude Desktop |
| Connecting to AI Assistants | Claude Code, Cursor, Codex, HTTP/Docker/systemd |
| Using the Skill | Install the MikroMCP usage skill so your assistant drives the tools safely |
| Available Tools | All 133 tools — parameters and example prompts |
| Architecture | System layers, request pipeline, auth model |
| Error Handling | Error categories, retry engine, circuit breaker |
| [Sec
Only the beginning is shown; read the rest in the repo