← Index

MikroTik RouterOS

io.github.StefanKnol/mikrotik-mcpv0.2.0Other

MikroTik RouterOS over the binary API, addressing rules by real .id not list position.

The current version, v0.2.0, was published to the official MCP registry on 2026-09-15. It is distributed as mikrotik-mcp on PyPI, filed under Other by this index, and declares 7 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using MikroTik RouterOS in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Auditable install path →Watch it hold a drift →
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-16).

Contracts can change after screening, with no version bump. The gate pins MikroTik RouterOS’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
MIKROTIK_HOST
required

IP address or hostname of the router, e.g. 192.168.88.1

MIKROTIK_USERNAME
required

RouterOS user. Use a dedicated account rather than admin; its group must carry the `api` policy, and a group without it is rejected with the same error as a wrong password.

MIKROTIK_PASSWORD
requiredsecret

Password for that user.

MIKROTIK_PORT

API port: 8729 for api-ssl (default), 8728 for plaintext.

MIKROTIK_TLS

Use the TLS API. Defaults to true; turning it off sends the router password over the network in the clear.

MIKROTIK_TLS_FINGERPRINT

SHA-256 of the router certificate. MikroTik's API-SSL certificate is self-signed, so pinning this is what makes the connection authenticated rather than merely encrypted.

MIKROTIK_TIMEOUT

Connection timeout in seconds. Defaults to 10.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
15
installability
25
documentation
15
stability
5
Alternatives in Other
AgentRoam
ai.agentroam/agentroam

Buy travel eSIMs, gift cards and mobile top-ups with crypto — user confirms before any order.

Authoryze
ai.authoryze/authoryze

Give your AI agent a spending limit: approval controls and single-use virtual cards.

Stelar Signals
io.github.StelarDigital/stelar-signals-mcp

Crypto market signals and portfolio telemetry. 6 tools pay-per-call in USDC, no API key.