Topolograph MCP Server

Topolograph MCP server exists for a simple reason — assistants are far more useful when they can act on Topolograph directly instead of describing what you should do. A Model Context Protocol (MCP) server that provides access to Topolograph API for OSPF/IS-IS network analysis.

What you get

This MCP server enables AI agents to interact with Topolograph API to analyze network topologies, monitor events, and perform path calculations for OSPF and IS-IS protocols. MCP (Model Context Protocol) is essential for connecting Large Language Models (LLMs) to network infrastructure, allowing AI agents to query and analyze network data in real-time.

• Graph Management — Retrieve and upload network graphs
• Network Analysis — Query network information by IP, node ID, or network mask
• Event Monitoring — Track network and adjacency events with time filtering
• Path Calculation — Calculate shortest paths between nodes with backup path support
• Status Monitoring — Check graph connectivity and health status
• Node/Edge Queries — Retrieve detailed node and edge information from diagrams

What the assistant can call

Once Topolograph is connected, these are the calls the assistant has available:

• get_all_graphs — List available graphs with filtering options
• get_graph_by_time — Fetch specific graph by time
• get_network_by_graph_time — Query network information
• get_graph_status — Check graph health and connectivity
• get_network_events — Retrieve network up/down events
• get_adjacency_events — Get node/host and link events
• get_events_timeline — Node/host events grouped into time waves for incident narration
• get_nodes — Query diagram nodes (filter by role flags: ABR/ASBR, IS-IS overload/attached)
• get_edges — Query diagram edges (include=["lsp_left_bw", "lsps", "is_te_link", "edge_key"] for MPLS TE fields)
• get_shortest_path — Calculate the shortest path between two nodes (with_lsps=true to account for autoroute-enabled MPLS-TE tunnels)
• get_edge_failure_reaction — Predict whole-network impact if one or more links go down
• upload_graph — Upload new graphs to the API

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need 2 environment variables: TOPOLOGRAPH_API_BASE, TOPOLOGRAPH_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Topolograph's toolset — get_all_graphs, get_graph_by_time, get_network_by_graph_time and 10 more — is a fair guide to whether it matches your workflow. It is maintained by vadims06; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Topolograph.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the topolograph mcp server does with a few real requests.