Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-alikarami-mikromcp-alikarami": {
"args": [
"-y",
"mikromcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
AI-native network automation for MikroTik RouterOS. MikroMCP exposes RouterOS as a typed, auditable Model Context Protocol server so Claude, Cursor, Codex, and other MCP clients can inspect, diagnose, and safely operate MikroTik routers in natural language.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'mikromcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked mikromcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops / security
MCP server for using the GitLab API
MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Governed MCP workflows with policy validation, findings tracking, and review gates.
MCP Security Weekly
Get CVE alerts and security updates for io.github.AliKarami/mikromcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
AI-native network automation for MikroTik RouterOS. MikroMCP exposes RouterOS as a typed, auditable Model Context Protocol server so Claude, Cursor, Codex, and other MCP clients can inspect, diagnose, and safely operate MikroTik routers 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.
| 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 |
| 🔐 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 |