About RouterOS MCP
RouterOS MCP is an MCP server in the Healthcare category: mCP server for MikroTik RouterOS enabling standardized config, controlled services, continuous health insight, and policy guardrails for reliable, repeatable ops.
Install
git clone https://github.com/grammy-jiang/RouterOS-MCPThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about RouterOS MCP
Powered by Claude · Grounded in docs
Security checks
- ✓README presentThe repository ships documentation.
5 checks have not been run yet.
README
RouterOS MCP Service
Model Context Protocol (MCP) service for managing multiple MikroTik RouterOS v7 devices. Expose safe, auditable network operations to ChatGPT, Claude Desktop, and other AI tools with strong security guardrails, role-based authorization, and built-in approval workflows.
Features
- 66 Production-Ready Tools – System status, interfaces, IP, routing, firewall, wireless, DHCP, bridge, and diagnostics
- Multi-Device Fleet Management – Manage multiple RouterOS v7 devices from a single service instance
- Three-Tier Security Model – Role-based access control, per-device capability flags, OAuth 2.1/OIDC authentication
- Safe Configuration Changes – Plan/apply workflow with HMAC-signed approval tokens, automatic rollback, and health checks
- Environment Separation – Lab, staging, production modes with tool restrictions and safety guardrails
- Full Observability – Structured logging, Prometheus metrics, OpenTelemetry tracing, 80%+ test coverage
Quick Start
Prerequisites
- Python 3.11 or later
- MikroTik RouterOS v7 device(s) with REST API enabled
- (Optional) Claude Desktop or MCP-compatible client
Installation
git clone https://github.com/grammy-jiang/RouterOS-MCP.git
cd RouterOS-MCP
uv sync
Or with dev dependencies for testing:
uv sync --all-extras
Run STDIO Server
For local development with Claude Desktop:
routeros-mcp --config config/lab.yaml
The server uses JSON-RPC over stdin/stdout. Configure your MCP client to connect.
Register a Device
routeros-mcp device add \
--name lab-router \
--hostname 192.168.88.1 \
--rest-user admin \
--rest-password secret
Run Tests
# Quick smoke test (6 seconds)
uv run pytest tests/unit -q
# Full suite with coverage (21 seconds)
uv run pytest
Documentation
Comprehensive design documentation in docs/:
| Topic | Document |
|---|---|
| Getting Started | Development Setup, Requirements |
| Architecture | System Design & Architecture, Implementation Layout |
| Security & Auth | Security Model, OAuth Setup (Azure/Okta/Auth0) |
| MCP Integration | MCP Protocol, Tools Catalog, Resources & Prompts |
| Operations | Admin CLI, HTTP/SSE Deployment, Production Runbook |
| Testing | Testing Strategy, Performance Testing |
| Contributing | Contribution Guidelines |
| Implementation | All 20 Design Docs – Phase planning, database schema, error codes, module specifications |
Project Status
Phase 4 Complete (January 2026):
- ✅ 66 MCP tools (read + write + diagnostics) with role-based authorization
- ✅ STDIO and HTTP/SSE transports fully functional
- ✅ Multi-device coordination with staged rollouts
- ✅ Plan/apply framework with HMAC-signed approval tokens
- ✅ 12+ MCP resources and 8 guided workflow prompts
- ✅ Admin CLI for device and plan management
- ✅ Full observability (structured logging, metrics, tracing)
- ✅ 583 tests (564 unit + 19 e2e), 80%+ coverage
Planned (Phase 5):
- Multi-user role-based access control (RBAC)
- OAuth Authorization Code flow with PKCE
- Per-user device scopes and approval workflows
- Compliance reporting and policy enforcement
Support & Community
- Issues – GitHub Issues for bug reports and feature requests
- Discussions – GitHub Discussions for questions and ideas
- Contributing – See CONTRIBUTING.md for development guidelines and setup instructions
License
MIT License – see LICENSE for details.
README copy captured when this server was indexed; it may lag the repository. The original is authoritative.