← Index

io.github.wiresage/mikrotik-mcp

io.github.wiresage/mikrotik-mcpv0.24.2.0Other

MCP server for MikroTik routers: firewall, NAT, routing, DHCP, DNS, WireGuard and more via SSH.

The current version, v0.24.2.0, was published to the official MCP registry on 2026-10-11. It is distributed as mcp-server-mikrotik on PyPI, filed under Other by this index, and declares 9 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 io.github.wiresage/mikrotik-mcp 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
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-10-12).

Contracts can change after screening, with no version bump. The gate pins io.github.wiresage/mikrotik-mcp’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

IP address or hostname of the MikroTik router (single-device mode; default: 127.0.0.1). Not needed when an inventory is configured.

MIKROTIK_USERNAME

SSH username for the MikroTik router (single-device mode; default: admin)

MIKROTIK_PASSWORD
secret

SSH password for the MikroTik router (single-device mode)

MIKROTIK_PORT

SSH port of the MikroTik router (single-device mode; default: 22)

MIKROTIK_KEY_FILENAME

Path to SSH private key file for key-based authentication (single-device mode)

MIKROTIK_READ_ONLY

When true, expose only tools that do not modify RouterOS or its file store. Use a read-only RouterOS account as defence in depth.

MIKROTIK_SENSITIVE_HIDING

When true, redact recognized credentials and private key material from tool results, MCP notifications, and logs, and omit tools that return opaque sensitive payloads.

MIKROTIK_INVENTORY_FILE

Path to a YAML file listing multiple MikroTik devices (title, host, port, username, password, key_filename, tags, region). See docs/reference/inventory.

MIKROTIK_INVENTORY
secret

Inline multi-device inventory as a YAML (or JSON) list; takes precedence over MIKROTIK_INVENTORY_FILE and the single-device variables. Holds credentials.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
10
installability
25
documentation
15
stability
5
Alternatives in Other