Same collection group
SigNoz MCP
Query SigNoz logs, traces, metrics, alerts, dashboards, and service telemetry through its official MCP server.
MCPby VictoriaMetrics · VictoriaMetrics/mcp-victoriametrics
Query VictoriaMetrics metrics and time series, inspect alerts and cardinality, and search the embedded product documentation.
{
"mcpServers": {
"victoriametrics": {
"command": "/path/to/mcp-victoriametrics",
"env": {
"VM_INSTANCE_ENTRYPOINT": "<YOUR_VM_INSTANCE>",
"VM_INSTANCE_TYPE": "<YOUR_VM_INSTANCE_TYPE>",
"VM_INSTANCE_BEARER_TOKEN": "<YOUR_VM_BEARER_TOKEN>",
"VM_INSTANCE_HEADERS": "<HEADER>=<HEADER_VALUE>,<HEADER>=<HEADER_VALUE>"
}
}
}
}Sources: Author README · Checked 2026-10-14.
The placeholders describe alternative deployment and authentication settings. Use only the settings required by your instance; the README also documents a Docker distribution.
Sources: Author README · Checked 2026-10-14.
| Capability | What it does |
|---|---|
| query | Run instant PromQL or MetricsQL queries. |
| query_range | Evaluate a metric over a time interval. |
| alerts | Inspect firing and pending alerts. |
| tsdb_status | Examine time-series cardinality statistics. |
Sources: Author README · Checked 2026-10-14.
Suggested prompts for your own client. These are examples, not recorded tool executions.
Run a range query for a metric I choose and explain how its values changed during my incident window.Inspect current alerts and cardinality statistics, then identify the evidence needed before changing monitoring configuration.Author README, linked first-party setup instructions and public repository metadata reviewed on 2026-10-14. No third-party package was installed, no MCP server was executed, and no hosted service was connected.
Recent activity refers to the repository push timestamp. It does not establish the product’s original release date. Stars are a dated snapshot of the entire repository.