mikrotik-rest-mcp-server

Purpose: Managing MikroTik RouterOS devices through REST APIs without unsafe or unguarded network mutations.

Inferred · not functionally tested

Audience: network administrators and developers managing MikroTik RouterOS devices

Inferred · not functionally tested

Functions: agents, workflow_automation

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

In the Frameworks & runtimes space, mikrotik-rest-mcp-server takes a focused approach. Inferred · not functionally tested: It focuses on managing MikroTik RouterOS devices through REST APIs without unsafe or unguarded network mutations. Inferred · not functionally tested: mikrotik-rest-mcp-server is an open-source project aimed at network administrators and developers managing MikroTik RouterOS devices. Basis unknown · not verified: mikrotik-rest-mcp-server is open source under the MIT license. Basis unknown · not verified: mikrotik-rest-mcp-server is available on the command line, and it can be self-hosted.

Behind mikrotik-rest-mcp-server is Sogl, and it first shipped in 2026. Development happens publicly on GitHub with 5 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include filtered reads, guarded mutations, and timed rollback. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.