Server facts
mikromcp MCP Server
Project
- Author
- AliKarami
- Repository
- github.com/AliKarami/MikroMCP
- License
- Not specified
- Category
- Cloud & DevOps
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 79
- Last commit
- Data as of
Tags
- Claude
- Cursor
- Devops
- ai agents
- codex
- infrastructure
- mikrotik
- network automation
- networking
- routeros
Overview
MikroTik network operations in MikroMCP span device inspection, connectivity diagnosis, and configuration changes through clients such as Claude Desktop, Cursor, and Codex. Operators can examine resource consumption, interface traffic, DHCP leases, firewall behavior, routing sessions, and VPN peers. Ping, traceroute, traffic snapshots, and filtered logs support troubleshooting, while management tools cover addressing, DNS, wireless settings, bridges, routing policies, and local accounts. Router maintenance includes configuration exports, backups, package updates, scripts, and scheduled jobs. SwOS tools expose switch status and decoded endpoint data alongside endpoint write operations.
For coordinated changes, operators can preview an ordered set of writes against current device state, then apply it with execution stopping at the first failure. Applied steps receive individual snapshots and journal entries that support rollback. Fleet execution targets configured router IDs or tags and reports results for each router; destructive fleet actions use a confirmation-token flow. SwOS writes default to preview mode and retain the previous endpoint data for restoration. The server communicates over stdio, and its router registry inspection reveals targeting information without returning credentials.
mikromcp setup notes
- mikromcp records stdio only; confirm a network transport upstream before planning remote access.
- mikromcp has no recorded license; confirm reuse terms in its repository.