Model Context Protocol

Network Documentation MCP Servers

A headless index of vendor networking manuals — currently MikroTik RouterOS and Juniper Junos OS — exposed to LLM clients over MCP. Each server does hybrid keyword + semantic search across its source's docs and returns the canonical manual URL with every result, so an assistant can link straight to the real page.

Index status

Current size of the local documentation index, per source.

MikroTik RouterOS Manual mikrotik
Pages indexed 1,839
Categories 21
Chunks embedded 11,561
Last sync completed · 1 week ago
Juniper Junos OS Documentation juniper
Pages indexed 2,504
Categories 75
Chunks embedded 29,785
Last sync running · 1 week ago

MCP servers

Each source is served by its own MCP server, both exposing the same set of search & browse tools — an MCP client discovers those directly, so they aren't duplicated here. Every tool is read-only: none of them can modify the index or anything else.

Searches a local mirror of manual.mikrotik.com (the RouterOS manual). A page's external_id is its slug (the URL path after /docs/, e.g. virtual-private-networks/wireguard), and its category is the first path segment (e.g. routing-and-networking-protocols).

Connecting a client

The server is exposed over streamable HTTP. Point your MCP client at this endpoint (HTTP POST): 

https://netdocs.axb.nu/mcp/mikrotik-docs

Most clients take an mcpServers map (e.g. an .mcp.json file): 

{
    "mcpServers": {
        "mikrotik-docs": {
            "type": "http",
            "url": "https://netdocs.axb.nu/mcp/mikrotik-docs"
        }
    }
}

Notes

The RouterOS manual is crawled in full on every sync, so this source's coverage is complete and stays current with upstream.

Searches a local mirror of the Juniper Junos OS documentation (crawled from juniper.net and converted to markdown). A page's external_id is its full source URL rather than a slug, and its category is derived from the Junos OS URL path (e.g. bgp).

Connecting a client

The server is exposed over streamable HTTP. Point your MCP client at this endpoint (HTTP POST): 

https://netdocs.axb.nu/mcp/juniper-docs

Most clients take an mcpServers map (e.g. an .mcp.json file): 

{
    "mcpServers": {
        "juniper-docs": {
            "type": "http",
            "url": "https://netdocs.axb.nu/mcp/juniper-docs"
        }
    }
}

Notes

The Junos OS documentation is crawled in full on every sync, so this source's coverage is complete and stays current with upstream.