Mikrotik
Operate MikroTik RouterOS gear from your coding agent via the official API instead of clicking Winbox for every change.
Overview
io.github.marcelo-ochoa/mikrotik is a MCP server for the Operate phase that connects agents to the MikroTik RouterOS API for network infrastructure tasks.
What is this MCP server?
- MCP bridge to MikroTik RouterOS API
- npm package @marcelo-ochoa/server-mikrotik with stdio transport
- Positional host argument plus MK_USER and MK_PASSWORD environment variables
- Version 1.0.6 in MCP server schema
- Source in github.com/marcelo-ochoa/servers (subfolder src/mikrotik)
- Server version 1.0.6
- Required env: MK_USER, MK_PASSWORD (secret); positional host argument
- npm identifier @marcelo-ochoa/server-mikrotik, stdio transport
What problem does it solve?
Builders who rely on MikroTik routers lack a safe, agent-native way to run RouterOS API operations without manual Winbox or one-off scripts.
Who is it for?
Solo operators managing MikroTik edge routers, lab networks, or small-business connectivity from an AI coding environment.
Skip if: Teams on non-MikroTik stacks, pure cloud-only VPC management, or unattended production changes without review gates.
What do I get? / Deliverables
After registration, your agent can invoke MikroTik API operations through MCP using host and MK_USER/MK_PASSWORD configuration.
- MCP tools backed by live MikroTik RouterOS API calls
- Agent-driven network inspection and configuration workflows
- Documented host and credential wiring in the agent MCP config
Recommended MCP Servers
Journey fit
Router and network control is production operations work, which belongs in Operate when the product or homelab is already live. Infra subphase covers routers, firewalls, and edge networking that solo builders still manage without a platform team.
How it compares
RouterOS API MCP bridge, not a Terraform provider or generic SSH skill.
Common Questions / FAQ
Who is io.github.marcelo-ochoa/mikrotik for?
Solo builders and indie operators who run MikroTik RouterOS and want Claude Code or Cursor to call the RouterOS API via MCP.
When should I use io.github.marcelo-ochoa/mikrotik?
Use it in Operate infra work when diagnosing routes, firewall rules, or interfaces on live MikroTik hardware you already control.
How do I add io.github.marcelo-ochoa/mikrotik to my agent?
Install @marcelo-ochoa/server-mikrotik, add a stdio MCP entry with the router host argument, set MK_USER and MK_PASSWORD in the server env, restart the client, and approve MikroTik tools.