This project provides a Model Context Protocol (MCP) server that allows language models and other MCP clients to interact with a SuzieQ network
This project provides a Model Context Protocol (MCP) server that allows language models and other MCP clients to interact with a SuzieQ network observability instance via its REST API. Exposed over MCP by the suzieq mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
The server exposes SuzieQ's commands as MCP tools: - run_suzieq_show: Access the 'show' command to query detailed network state tables - run_suzieq_summarize: Access the 'summarize' command to get aggregated statistics and summaries
Everything the assistant can do here goes through one of these:
table — (String, Required) The SuzieQ table name (e.g., "device", "interface", "bgp")filters — (Dictionary, Optional) Key-value pairs for filtering (e.g., "hostname": "leaf01"). Omit or use {} for no filtersReturns — A JSON string with the results or an errorYou will need 2 environment variables: PYTHONUTF8, SUZIEQ_API_KEY. 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.
http://your-suzieq-host:8000/api/v2) and a valid API keyThe server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Suzieq MCP's toolset — table, filters, Returns — is a fair guide to whether it matches your workflow. It is maintained by PovedaAqui; 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.
| Tool | What it does |
|---|---|
| table | (String, Required) The SuzieQ table name (e.g., "device", "interface", "bgp"). |
| filters | (Dictionary, Optional) Key-value pairs for filtering (e.g., "hostname": "leaf01"). Omit or use {} for no filters. |
| Returns | A JSON string with the results or an error. |
{
"mcpServers": {
"suzieq": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"PYTHONUTF8": "your-value",
"SUZIEQ_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
http://your-suzieq-host:8000/api/v2) and a valid API key| Variable | Description | Required |
|---|---|---|
| PYTHONUTF8 | Configuration value read at startup. | Optional |
| SUZIEQ_API_KEY | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.