routeros-inspector-mcp
A constrained, read-only MCP server for MikroTik RouterOS inventory inspection and policy-backed audits.
README
routeros-inspector-mcp
A constrained, read-only MCP server for MikroTik RouterOS inventory inspection and policy-backed audits.
The server is fixture-only by default. Live access requires an explicit --live flag, inventory-defined devices, read-only credentials, and fail-closed transport configuration. It does not expose arbitrary RouterOS commands or mutation tools.
Safety model
- No arbitrary command execution
- No mutation, reboot, restore, firmware, or user-management tools
- No caller-supplied hosts or IP addresses; callers select inventory device IDs only
- Fixture-only operation unless
--liveis explicitly supplied - Verified API-SSL with pinned CA trust, hostname verification, and TLS 1.2+
- No plaintext downgrade when TLS is configured
- Allowlisted client errors and redacted outputs
- Bounded audit fan-out
- Stdio by default; optional HTTP is forced to
127.0.0.1
See docs/deployment.md for the complete deployment boundary and CHANGELOG.md for release history.
Requirements
- Python 3.11+
- RouterOS 7 for live API use
ansible-vaultonly when using the included Vault credential provider
Installation
python -m venv .venv
. .venv/bin/activate
python -m pip install -e '.[test]'
Fixture-first quick start
The checked-in inventory, policy, and RouterOS data are purpose-built synthetic examples. They contain no live-derived topology.
routeros-inspector list-devices --summary
routeros-inspector audit \
--devices edge-router,core-switch \
--audits vlan_consistency,wan_failover_state,snmp_scope \
--summary
python scripts/smoke_mcp_fixture.py
python -m routeros_inspector_mcp.server --transport stdio
Fixture mode never constructs a live RouterOS backend, even if an explicitly supplied inventory declares live transports.
Configuration
Copy the synthetic examples before configuring live access:
cp config/devices.example.yaml config/devices.yaml
cp config/policy.example.yaml config/policy.yaml
config/devices.yaml and config/policy.yaml are ignored because real inventories and policies reveal operational details. Keep certificates and live captures outside the repository.
A verified API-SSL inventory entry looks like:
devices:
edge-router:
role: gateway
risk: critical
host: router.example.net
transport: api
credential_ref: vault_mikrotik_readonly
allowed: true
routeros_api_port: 8729
routeros_api_tls: true
routeros_api_certificate: /absolute/path/to/router-ca.pem
routeros_api_server_name: router.example.net
TLS mode requires TCP/8729, a readable CA/certificate path, and a nonempty DNS name or IP SAN identity. Configuration errors fail closed and never trigger plaintext fallback.
Credential provider
The included provider resolves <credential_ref>_username and <credential_ref>_password from an Ansible Vault without logging values. Configure it with:
export ROUTEROS_INSPECTOR_VAULT_DIR="$HOME/.config/routeros-inspector-mcp"
export ROUTEROS_INSPECTOR_VAULT_FILE="vault.yml"
export ROUTEROS_INSPECTOR_VAULT_PASSWORD_FILE=".vault_pass"
The two file variables may also be absolute paths. Use a dedicated RouterOS read-only identity. Do not use a personal administrator or write-capable credential.
MCP tools
The server exposes fixed collectors such as device summaries, interfaces, bridge VLANs, routes, firewall tables, DHCP/ARP state, queues, WireGuard metadata, and IP services. It also exposes named audits for firmware, SNMP scope, STP, VLAN/trunk consistency, route ownership, WAN failover, encrypted DNS, QoS/DSCP, and backup metadata.
Tool responses omit connection details and credential references. Sensitive RouterOS fields are redacted.
Private fixture capture
scripts/refresh_routeros_fixture.py can transform an existing private artifact directory without network access. Live collection additionally requires the explicit --capture-live flag and explicit Ansible root, inventory, playbook, and Vault password paths. Captures still reveal topology and policy and default to the ignored artifacts/private-fixtures/ directory. Never copy them into tests/fixtures/routeros/ or commit them. Public tests must use purpose-built synthetic fixtures.
Development
make ci
Equivalent commands:
ruff check .
pytest -n auto -q
python -m compileall -q src tests
Security
Please read SECURITY.md before enabling live mode. Report vulnerabilities privately rather than opening a public issue.
License
MIT — see LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。