SigNoz MCP server: access metrics, traces, logs, alerts, and dashboards via AI assistants
SigNoz MCP server: access metrics, traces, logs, alerts, and dashboards via AI assistants. That is what the signoz mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
A Model Context Protocol (MCP) server that provides seamless access to SigNoz observability data through AI assistants and LLMs. Query metrics, traces, logs, alerts, dashboards, and services using natural language.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The server publishes 14 tools. What each one is for:
signoz_list_metrics — Discover active metric names and catalog metadatasignoz_query_metrics — Query known metrics for values, trends, breakdowns, or formulassignoz_get_top_metrics — Return top 100 metrics ranked by ingested sample volume with pre-computed percentages for cost and volume analysissignoz_check_metric_usage — Given a list of metric names (up to 50 per call), return which dashboards and alerts reference each onesignoz_check_metric_cardinality — Return label/attribute keys for a single metric with cardinality counts and sample values, sorted highest-cardinality firstsignoz_get_field_keys — Discover available field keys for metrics, traces, or logssignoz_get_field_values — Get possible values for a field keysignoz_list_alerts — List firing/silenced/inhibited Alertmanager alert instances (not rule definitions)signoz_list_alert_rules — List configured alert-rule summaries, including inactive/OK and disabled rulessignoz_get_alert — Get one alert rule's full definition by idsignoz_get_alert_history — Get one rule's firing or state-transition historysignoz_create_alert — Create a v2 direct/policy-routed alert or a direct-routed v1 anomaly alertConfiguration is passed through the environment: SIGNOZ_URL, SIGNOZ_API_KEY, LOG_LEVEL, MCP_SERVER_HOST, OAUTH_TOKEN_SECRET, OAUTH_ISSUER_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
signoz_check_metric_usage (it reads v2/Perses dashboards for dashboard usage; on older versions the dashboard half is silently empty, though alert usage alone works from v0.131.0) -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. SigNoz's toolset — signoz_list_metrics, signoz_query_metrics, signoz_get_top_metrics and 11 more — is a fair guide to whether it matches your workflow. It is maintained by SigNoz; 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 |
|---|---|
| signoz_list_metrics | Discover active metric names and catalog metadata |
| signoz_query_metrics | Query known metrics for values, trends, breakdowns, or formulas |
| signoz_get_top_metrics | Return top 100 metrics ranked by ingested sample volume with pre-computed percentages for cost and volume analysis |
| signoz_check_metric_usage | Given a list of metric names (up to 50 per call), return which dashboards and alerts reference each one |
| signoz_check_metric_cardinality | Return label/attribute keys for a single metric with cardinality counts and sample values, sorted highest-cardinality first |
| signoz_get_field_keys | Discover available field keys for metrics, traces, or logs |
| signoz_get_field_values | Get possible values for a field key |
| signoz_list_alerts | List firing/silenced/inhibited Alertmanager alert *instances* (not rule definitions) |
| signoz_list_alert_rules | List configured alert-rule summaries, including inactive/OK and disabled rules |
| signoz_get_alert | Get one alert rule's full definition by id |
| signoz_get_alert_history | Get one rule's firing or state-transition history |
| signoz_create_alert | Create a v2 direct/policy-routed alert or a direct-routed v1 anomaly alert |
| signoz_update_alert | Fully replace an existing alert rule by id |
| signoz_delete_alert | Permanently delete a confirmed alert rule by UUIDv7 id |
```json
{
"mcpServers": {
"signoz": {
"url": "http://localhost:8000/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
signoz_check_metric_usage (it reads v2/Perses dashboards for dashboard usage; on older versions the dashboard half is silently empty, though alert usage alone works from v0.131.0) -| Variable | Description | Required |
|---|---|---|
| SIGNOZ_URL | Endpoint or connection string the server talks to. | Yes |
| SIGNOZ_API_KEY | Credential the server authenticates with. | Yes |
| LOG_LEVEL | Configuration value read at startup. | Optional |
| MCP_SERVER_HOST | Endpoint or connection string the server talks to. | Optional |
| OAUTH_TOKEN_SECRET | Credential the server authenticates with. | Yes |
| OAUTH_ISSUER_URL | Endpoint or connection string the server talks to. | 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.