The events timeline is what changes an incident review: node and link events grouped into waves and labelled outage, flap or up, so the order of events becomes a query rather than a log-reading exercise. The failure-reaction and CSPF calls sit on the other side of the same graph — what breaks if this link goes, and whether a constrained tunnel could exist at all, both answered without touching the network.
A query layer over the Topolograph API for OSPF and IS-IS networks: uploaded topology graphs, the events recorded against them, path calculations across them, and the MPLS traffic-engineering tunnels defined on them.
- get_all_graphs lists what has been uploaded with filters, get_graph_by_time fetches the topology as it stood at a moment, and upload_graph brings a new one in.
- get_network_by_graph_time queries network information by IP, node ID or mask, and get_graph_status reports connectivity and health.
- get_network_events returns network up and down events, get_adjacency_events returns node, host and link events, and get_events_timeline groups them into chronological waves labelled outage, flap or up.
- get_nodes filters diagram nodes by role flags — ABR and ASBR, IS-IS overload and attached — and get_edges returns edges, with MPLS TE fields such as reserved bandwidth and TE-link status available on request.
- get_shortest_path computes the path between two nodes with backup support, and can account for autoroute-enabled MPLS-TE tunnels rather than ignoring them.
- get_edge_failure_reaction predicts the whole-network impact of one or more links going down, before the change window rather than after.
- get_lsps, add_lsp, update_lsp and delete_lsp manage MPLS TE tunnels, filterable by status or by the node or edge they traverse.
- get_cspf_path answers whether a constrained path is even feasible between two nodes, without creating a tunnel to find out.
A running Topolograph API and its base URL in the environment as TOPOLOGRAPH_API_BASE; TOPOLOGRAPH_API_TOKEN is optional. Python with the listed dependencies, or take the docker-compose route from the topolograph-docker repository, which brings up the whole stack and wires this server to the API for you. It serves MCP over HTTP on port 8000 rather than stdio.