SigNoz MCP server
SigNoz's official MCP server gives agents full access to traces, logs, metrics, dashboards, and alerts in your OpenTelemetry-native stack.
The SigNoz MCP server is SigNoz's official integration that connects a coding agent to your OpenTelemetry-native observability data. SigNoz unifies traces, logs, and metrics in one place, and this server exposes that breadth as a large, well-organized tool surface so an agent can investigate an incident end to end: search and aggregate traces, search and aggregate logs, query metrics, inspect services and their top operations, and read or run the builder queries that power dashboards. It can also discover field keys and values, which lets an agent learn the shape of your telemetry before composing a query.
Beyond read access it manages the operational layer: listing, getting, creating, updating, and deleting alerts, dashboards, saved views, and notification channels, plus importing dashboards and listing dashboard templates. It runs over stdio or HTTP and ships several ways: a Go install, prebuilt binaries, and a Docker image (signoz/signoz-mcp-server), authenticating to a self-hosted instance with SIGNOZ_URL and a SIGNOZ_API_KEY. SigNoz Cloud users can instead point at the hosted remote endpoint at https://mcp.<region>.signoz.cloud/mcp with OAuth 2.1, so there are no long-lived API keys on disk. It even bundles documentation search tools so the agent can look up SigNoz setup guidance inline.
Quick install
Copy-paste configs are provided for all 8 supported clients. Pick your client below.
Available tools
| Tool | Description |
|---|---|
| signoz_list_metrics | Lists available metric keys in the SigNoz instance. |
| signoz_query_metrics | Queries metric time series and values. |
| signoz_list_alerts | Lists alerts in SigNoz. |
| signoz_list_alert_rules | Lists configured alert rules. |
| signoz_get_alert | Gets the details of a specific alert. |
| signoz_get_alert_history | Gets the firing history for an alert. |
| signoz_create_alert | Creates a new alert rule. |
| signoz_update_alert | Updates an existing alert rule. |
| signoz_delete_alert | Deletes an alert rule. |
| signoz_list_dashboards | Lists all dashboards. |
| signoz_get_dashboard | Gets the configuration of a specific dashboard. |
| signoz_create_dashboard | Creates a new dashboard. |
| signoz_update_dashboard | Updates an existing dashboard. |
| signoz_delete_dashboard | Deletes a dashboard. |
| signoz_import_dashboard | Imports a dashboard from a definition. |
| signoz_list_dashboard_templates | Lists available dashboard templates. |
| signoz_search_traces | Searches distributed traces with filters. |
| signoz_aggregate_traces | Aggregates trace data for analysis. |
| signoz_get_trace_details | Gets the full details of a specific trace. |
| signoz_search_logs | Searches logs with filters. |
| signoz_aggregate_logs | Aggregates log data for analysis. |
| signoz_list_services | Lists instrumented services. |
| signoz_get_service_top_operations | Gets the top operations for a service. |
| signoz_list_views | Lists saved explorer views. |
| signoz_get_view | Gets a specific saved view. |
| signoz_create_view | Creates a new saved view. |
| signoz_update_view | Updates a saved view. |
| signoz_delete_view | Deletes a saved view. |
| signoz_get_field_keys | Lists available field keys for telemetry filtering. |
| signoz_get_field_values | Lists values for a given field key. |
| signoz_search_docs | Searches SigNoz documentation for setup and configuration guidance. |
| signoz_fetch_doc | Fetches the full content of a SigNoz documentation page. |
| signoz_list_notification_channels | Lists configured notification channels. |
| signoz_get_notification_channel | Gets a specific notification channel. |
| signoz_create_notification_channel | Creates a new notification channel. |
| signoz_update_notification_channel | Updates a notification channel. |
| signoz_delete_notification_channel | Deletes a notification channel. |
| signoz_execute_builder_query | Executes a raw query-builder query for advanced telemetry analysis. |
Required configuration
- SIGNOZ_URLRequired
URL of your SigNoz instance. Required for stdio mode; optional when using OAuth on the remote endpoint.
- SIGNOZ_API_KEYRequired
SigNoz API key from Settings -> API Keys. Required for stdio mode; optional with OAuth.
- TRANSPORT_MODEOptional
MCP transport mode: stdio (default) or http.
- LOG_LEVELOptional
Logging level: info (default), debug, warn, or error.
- OAUTH_ENABLEDOptional
Enable the OAuth 2.1 authentication flow for HTTP transport.
What you can do with it
Trace an incident across signals
Let the agent search_traces to find the failing request, get_trace_details to see the span breakdown, then search_logs and query_metrics around the same window to correlate logs and saturation in one investigation.
Manage alerts and dashboards from chat
Have the agent list and update alert rules, create dashboards from templates with import and create tools, and wire up notification channels, all without leaving the editor.
FAQ
- Is it free?
- Yes. The SigNoz MCP server is open source under Apache-2.0 and free to run. You only need a SigNoz instance, which can be self-hosted (also open source) or SigNoz Cloud.
- Does it support remote/OAuth?
- Yes. SigNoz Cloud users can use the hosted remote endpoint at https://mcp.<region>.signoz.cloud/mcp with OAuth 2.1. Self-hosted users run it locally over stdio or HTTP with SIGNOZ_URL and a SIGNOZ_API_KEY.
- What can it actually do?
- A lot: search and aggregate traces and logs, query metrics, inspect services, and full CRUD on alerts, dashboards, saved views, and notification channels, plus built-in documentation search.