MCP server for MikroTik RouterOS: typed tools, dry-run, RBAC, audit logs, and rollback.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-alikarami-mikromcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for MikroTik RouterOS: typed tools, dry-run, RBAC, audit logs, and rollback.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe 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
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.
Enhanced MCP server for GitLab: group projects listing and activity tracking
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.

| Instead of... | MikroMCP gives you... |
|---|---|
| Hand-written RouterOS CLI snippets from chat | Typed MCP tools with strict Zod validation |
| Blind config changes | Dry-run previews, idempotency checks, snapshots, and rollback tooling |
| One-off scripts per router | A multi-router registry with per-router credentials, tags, TLS, SSH, and maintenance windows |
| Raw network access for every assistant | RBAC identities, bearer tokens for HTTP mode, tool allowlists, and audit trails |
| Fragile troubleshooting workflows | Router-originated ping, traceroute, torch, logs, interfaces, DHCP, firewall, routes, WiFi, WireGuard, and more |
| Category | What MikroMCP covers |
|---|---|
| 🧭 Router management | System status, clock, reboot, packages, files, scripts, scheduler jobs, containers |
| 🌐 Network operations | Int |