run_suzieq_showLABSCO SUMMARY
Two tools, and the table name carries the whole surface.
Rather than one tool per network object, the design passes the table as an argument — so anything SuzieQ indexes is reachable without the server growing. The pairing matters: show for the rows, summarize for the shape of them, same filters on both. The one setup trap is documented and easy to hit: the credentials live in a .env file next to the entry point, so a client launching from elsewhere needs the working directory set.
What it is
An MCP server that fronts the SuzieQ REST API, exposing SuzieQ's two core commands as tools. Any table SuzieQ tracks — devices, interfaces, BGP, routes — is reachable, with the same filter semantics you would use in the CLI.
What you get
- Detailed network state from any SuzieQ table, with optional key-value filters such as hostname, VRF or state, returned as a JSON string —
run_suzieq_show - Aggregated statistics and summaries over the same tables and filters, for when the per-row detail is not the question —
run_suzieq_summarize
Requirements
A running SuzieQ instance with its REST API enabled, plus the endpoint and an access token — SUZIEQ_API_ENDPOINT and SUZIEQ_API_KEY, both read from a .env file in the project directory. Python 3.8 or higher and uv; dependencies are mcp, httpx and python-dotenv. It runs over stdio via uv run python main.py. If you register it with a client, set the working directory to the project folder so the .env file is found.
Setup effort
Build from source
USE CASES
01
Checking BGP state across the fabric
Show the BGP table filtered to a hostname, or summarize sessions across all of them when you want the count of what is down.
02
Finding interfaces in the wrong state
Show the interface table filtered by VRF and state, so only the ones you care about come back.
03
Getting an inventory read on the network
Summarize the device table for the aggregate picture before drilling into any one box.
2 tools
Listed in project docs. Your client may show a different list.
run_suzieq_summarizeBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- Python 3.8 or later
- SUZIEQ_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"suzieq-server": {
"command": "uv",
"args": [
"run",
"python",
"<YOUR_PATH_TO_PROJECT>/mcp-suzieq-server/main.py"
],
"workingDirectory": "<YOUR_PATH_TO_PROJECT>/mcp-suzieq-server/"
}
}
}The configuration on this page does not set SUZIEQ_API_KEY; the project's instructions put it in a .env file. Check which folder the server reads that file from before you rely on it.
