get_all_graphsLABSCO SUMMARY
Topology questions answered from the recorded graph, including the ones you would rather not test in production.
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.
What it is
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.
What you get
- 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.
Requirements
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.
Setup effort
Build from source — git clone https://github.com/Vadims06/topolograph-docker.git
USE CASES
01
Reconstructing what happened during an outage
Read the events grouped into waves, then drop to the underlying network and adjacency events when the summary is not enough.
02
Working out where traffic would reroute
Compute the shortest path between two nodes with its backup, on the topology as it was, optionally accounting for autoroute tunnels.
03
Deciding whether it is safe to take a link down
Ask what the whole network does if that link — or several — fails, before the maintenance window rather than during it.
04
Checking whether a new tunnel can exist before creating it
Run the constrained-path feasibility check between the two endpoints, then add the tunnel only if it comes back viable.
05
Auditing the MPLS TE tunnels already in place
List the tunnels by status or by the node or edge they cross, and remove or amend the ones that no longer belong.
06
Looking at the network as it was at a point in time
Fetch the graph for the moment in question and query it by IP or mask the way you would the live one.
07
Finding the routers that matter
Filter nodes by role — ABR, ASBR, overload or attached — and pull the edges between them with their TE fields.
17 tools
Listed in project docs. Your client may show a different list.
get_graph_by_timeget_network_by_graph_timeget_graph_statusget_network_eventsget_adjacency_eventsget_events_timelineget_nodesget_edgesget_shortest_pathget_edge_failure_reactionupload_graphget_lspsadd_lspupdate_lspdelete_lspget_cspf_pathBEFORE YOU INSTALL
What to know first
Tools you get
17 tools named in the project's documentation.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/Vadims06/topolograph-docker.git
cd topolograph-docker
docker-compose pull
docker-compose up -dPoint your MCP client at http://localhost:8000/mcp — the stack serves MCP over HTTP there and connects it to the Topolograph API for you
