SigNoz MCP Server

The SigNoz MCP Server implements the Model Context Protocol (MCP) — an open standard that lets AI assistants interact with your SigNoz observability data. Query metrics, traces, logs, alerts, and dashboards through natural language.

If you've already set up the MCP server, skip ahead to the use cases to see what you can do with it.

Connect to SigNoz's MCP server

Connect your AI tool to SigNoz Cloud's hosted MCP server. No installation required — just add the URL and authenticate.

https://mcp.<region>.signoz.cloud/mcp

Make sure you select the correct region that matches your SigNoz Cloud account. Using the wrong region will result in authentication failures.

<region>: Your SigNoz Cloud region. Find your region under Settings → Ingestion in SigNoz, or see the region reference.

Install in one click

Manual Configuration

Add this configuration to .cursor/mcp.json:

{
  "mcpServers": {
    "signoz": {
      "url": "https://mcp.<region>.signoz.cloud/mcp"
    }
  }
}

<region>: Your SigNoz Cloud region

Need help? See the Cursor MCP docs ↗

Install in one click

Manual Configuration

Add this configuration to .vscode/mcp.json:

{
  "servers": {
    "signoz": {
      "type": "http",
      "url": "https://mcp.<region>.signoz.cloud/mcp"
    }
  }
}

<region>: Your SigNoz Cloud region

Need help? See the VS Code MCP docs ↗

Configure

Run this command to add the SigNoz MCP server:

claude mcp add --scope user --transport http signoz https://mcp.<region>.signoz.cloud/mcp

<region>: Your SigNoz Cloud region

After configuring the MCP server, you need to authenticate. In a terminal run:

claude /mcp

Select the signoz server and complete the authentication flow.

Configure

Run this command to add the SigNoz MCP server:

codex mcp add signoz --url https://mcp.<region>.signoz.cloud/mcp

Or add this configuration to config.toml:

[mcp_servers.signoz]
url = "https://mcp.<region>.signoz.cloud/mcp"

<region>: Your SigNoz Cloud region

After adding the server, authenticate:

codex mcp login signoz

Then run /mcp inside Codex to verify the connection.

Configure

Add the MCP server via CLI:

gemini mcp add -t http signoz https://mcp.<region>.signoz.cloud/mcp

Or add this configuration to ~/.gemini/settings.json:

{
  "mcpServers": {
    "signoz": {
      "httpUrl": "https://mcp.<region>.signoz.cloud/mcp"
    }
  }
}

<region>: Your SigNoz Cloud region

After installation, start Gemini CLI and authenticate:

/mcp auth signoz

Configure

Add this configuration to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "signoz": {
      "serverUrl": "https://mcp.<region>.signoz.cloud/mcp"
    }
  }
}

<region>: Your SigNoz Cloud region

When prompted, complete the authentication flow.

Configure

Open the MCP Store via the ... menu in the agent panel.
Click Manage MCP Servers.
Add a new server with the SigNoz MCP URL: https://mcp.<region>.signoz.cloud/mcp

Or manually add to mcp_config.json:

{
  "mcpServers": {
    "signoz": {
      "serverUrl": "https://mcp.<region>.signoz.cloud/mcp"
    }
  }
}

<region>: Your SigNoz Cloud region

After saving the config, it will prompt you to complete the OAuth flow. To edit the config from within Antigravity, click the ... menu at the top of the Agent pane → MCP Servers → Manage MCP Servers → View raw config.

If you run into authentication issues, open the command palette and run Authentication: Remove Dynamic Authentication Providers to clear cached OAuth credentials and re-authenticate.

Authenticate from your client

When you add the hosted MCP URL to your client, the MCP client will initiate an authentication flow. You will be prompted to enter:

Your SigNoz instance URL (e.g., https://your-instance.signoz.cloud)
Your API key — go to Settings → Service Accounts in SigNoz, create a service account, and generate an API key (requires Admin role). See Service Accounts for details.

SigNoz Cloud's hosted MCP server uses OAuth 2.1 for client-to-MCP authentication. MCP clients discover the auth endpoints from the server metadata, dynamically register as an OAuth client using Dynamic Client Registration (DCR, RFC 7591) when supported, then use Authorization Code + PKCE. During the browser step, SigNoz asks for your SigNoz instance URL and service account API key; the MCP server validates those credentials and issues bearer/refresh tokens for future MCP requests.

SigNoz Cloud's MCP server also supports header-based authentication for clients that can't do OAuth, but the recommended approach is to use OAuth when possible for better security and token management.

Only Admin users can create API keys. If you don't see the option, contact your workspace administrator.

Header-Based Authentication

Some MCP clients (like Cursor Automations) run entirely in the cloud and cannot perform interactive OAuth authentication. For these clients, use header-based authentication by passing your API key and instance URL directly in the request headers.

If your MCP client doesn't support OAuth flows or stdio transport — for example, Cursor Automations: use this header-based configuration instead.

{
  "mcpServers": {
    "signoz": {
      "url": "https://mcp.<region>.signoz.cloud/mcp",
      "headers": {
        "SIGNOZ-API-KEY": "<your-api-key>",
        "X-SigNoz-URL": "<your-signoz-instance-url>"
      }
    }
  }
}

<region>: Your SigNoz Cloud region
<your-api-key>: API key from SigNoz Service accounts
<your-signoz-instance-url>: Your SigNoz Cloud instance URL

Keep your API key secure — never commit mcp.json to version control when it contains secrets.

For self-hosted SigNoz, you run the MCP server locally. The server supports two transport modes: Stdio (local binary, launched by the client) and HTTP (standalone server the client connects to over the network).

Fetch your API key

Log in to your SigNoz instance.
Go to Settings → Service Accounts.
Create a service account, open its Keys tab, click Add Key, and copy the generated key. See Service Accounts for details.

Only Admin users can create API keys. Keep your key secure — never commit it to version control.

Install the MCP server

Download the latest binary from GitHub Releases:

# macOS (Apple Silicon)
curl -L https://github.com/SigNoz/signoz-mcp-server/releases/latest/download/signoz-mcp-server_darwin_arm64.tar.gz | tar xz

# macOS (Intel)
curl -L https://github.com/SigNoz/signoz-mcp-server/releases/latest/download/signoz-mcp-server_darwin_amd64.tar.gz | tar xz

# Linux (amd64)
curl -L https://github.com/SigNoz/signoz-mcp-server/releases/latest/download/signoz-mcp-server_linux_amd64.tar.gz | tar xz

This extracts a signoz-mcp-server binary in the current directory. Move it somewhere on your PATH or note the absolute path for the config below.

go install github.com/SigNoz/signoz-mcp-server/cmd/server@latest

The binary is installed as server to $GOPATH/bin/ (default: $HOME/go/bin/server). You may want to rename it:

mv "$(go env GOPATH)/bin/server" "$(go env GOPATH)/bin/signoz-mcp-server"

docker pull signoz/signoz-mcp-server:latest

Run in HTTP mode:

docker run -p 8000:8000 \
  -e TRANSPORT_MODE=http \
  -e MCP_SERVER_PORT=8000 \
  -e SIGNOZ_URL=<your-signoz-url> \
  -e SIGNOZ_API_KEY=<your-api-key> \
  signoz/signoz-mcp-server:latest

<your-signoz-url>: Your self-hosted SigNoz instance URL (e.g., http://localhost:3301)
<your-api-key>: The API key from Fetch your API key

Docker always runs in HTTP transport mode. Use the HTTP tabs in the client setup below.

Configure your MCP client

Add the following to .cursor/mcp.json in your project root, or use Cursor → Settings → Tools & Integrations → + New MCP Server:

{
  "mcpServers": {
    "signoz": {
      "command": "<path-to-binary>/signoz-mcp-server",
      "args": [],
      "env": {
        "SIGNOZ_URL": "<your-signoz-url>",
        "SIGNOZ_API_KEY": "<your-api-key>",
        "LOG_LEVEL": "info"
      }
    }
  }
}

<path-to-binary>: Absolute path to the signoz-mcp-server binary
<your-signoz-url>: Your SigNoz instance URL
<your-api-key>: The API key from Fetch your API key

Start the MCP server in HTTP mode:

SIGNOZ_URL=<your-signoz-url> \
SIGNOZ_API_KEY=<your-api-key> \
TRANSPORT_MODE=http \
MCP_SERVER_PORT=8000 \
LOG_LEVEL=info \
./signoz-mcp-server

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "signoz": {
      "url": "http://localhost:8000/mcp"
    }
  }
}

Open Command Palette (Cmd+Shift+P / Ctrl+Shift+P) → MCP: Open User Configuration, then add:

{
  "servers": {
    "signoz": {
      "type": "stdio",
      "command": "<path-to-binary>/signoz-mcp-server",
      "args": [],
      "env": {
        "SIGNOZ_URL": "<your-signoz-url>",
        "SIGNOZ_API_KEY": "<your-api-key>",
        "LOG_LEVEL": "info"
      }
    }
  }
}

<path-to-binary>: Absolute path to the signoz-mcp-server binary
<your-signoz-url>: Your SigNoz instance URL
<your-api-key>: The API key from Fetch your API key

Open Copilot Chat in Agent mode and confirm you trust the server.

Start the MCP server in HTTP mode.
Add to VS Code MCP config:

{
  "servers": {
    "signoz": {
      "type": "http",
      "url": "http://localhost:8000/mcp"
    }
  }
}

Open Copilot Chat in Agent mode and confirm you trust the server.

Go to Settings → Developer → Edit Config and add to claude_desktop_config.json:

{
  "mcpServers": {
    "signoz": {
      "command": "<path-to-binary>/signoz-mcp-server",
      "args": [],
      "env": {
        "SIGNOZ_URL": "<your-signoz-url>",
        "SIGNOZ_API_KEY": "<your-api-key>",
        "LOG_LEVEL": "info"
      }
    }
  }
}

<path-to-binary>: Absolute path to the signoz-mcp-server binary
<your-signoz-url>: Your SigNoz instance URL
<your-api-key>: The API key from Fetch your API key

Start the MCP server in HTTP mode:

SIGNOZ_URL=<your-signoz-url> \
SIGNOZ_API_KEY=<your-api-key> \
TRANSPORT_MODE=http \
MCP_SERVER_PORT=8000 \
LOG_LEVEL=info \
./signoz-mcp-server

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "signoz": {
      "url": "http://localhost:8000/mcp"
    }
  }
}

claude mcp add --scope user signoz "<path-to-binary>/signoz-mcp-server" \
  -e SIGNOZ_URL="<your-signoz-url>" \
  -e SIGNOZ_API_KEY="<your-api-key>" \
  -e LOG_LEVEL=info

<path-to-binary>: Absolute path to the signoz-mcp-server binary
<your-signoz-url>: Your SigNoz instance URL
<your-api-key>: The API key from Fetch your API key

Use --scope project to limit to the current project. Remove with claude mcp remove signoz.

codex mcp add signoz \
  --env SIGNOZ_URL="<your-signoz-url>" \
  --env SIGNOZ_API_KEY="<your-api-key>" \
  --env LOG_LEVEL=info \
  -- "<path-to-binary>/signoz-mcp-server"

<path-to-binary>: Absolute path to the signoz-mcp-server binary
<your-signoz-url>: Your SigNoz instance URL
<your-api-key>: The API key from Fetch your API key

Edit ~/.codex/config.toml (global) or .codex/config.toml (project):

[mcp_servers.signoz]
command = "<path-to-binary>/signoz-mcp-server"
args = []

[mcp_servers.signoz.env]
SIGNOZ_URL = "<your-signoz-url>"
SIGNOZ_API_KEY = "<your-api-key>"
LOG_LEVEL = "info"

For HTTP mode via CLI or config.toml:

codex mcp add signoz --url http://localhost:8000/mcp

[mcp_servers.signoz]
url = "http://localhost:8000/mcp"

Add this configuration to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "signoz": {
      "command": "<path-to-binary>/signoz-mcp-server",
      "args": [],
      "env": {
        "SIGNOZ_URL": "<your-signoz-url>",
        "SIGNOZ_API_KEY": "<your-api-key>",
        "LOG_LEVEL": "info"
      }
    }
  }
}

<path-to-binary>: Absolute path to the signoz-mcp-server binary
<your-signoz-url>: Your SigNoz instance URL
<your-api-key>: The API key from Fetch your API key

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "signoz": {
      "command": "<path-to-binary>/signoz-mcp-server",
      "args": [],
      "env": {
        "SIGNOZ_URL": "<your-signoz-url>",
        "SIGNOZ_API_KEY": "<your-api-key>",
        "LOG_LEVEL": "info"
      }
    }
  }
}

<path-to-binary>: Absolute path to the signoz-mcp-server binary
<your-signoz-url>: Your SigNoz instance URL
<your-api-key>: The API key from Fetch your API key

Open Zed settings (Cmd+,) and add:

{
  "context_servers": {
    "signoz": {
      "command": "<path-to-binary>/signoz-mcp-server",
      "args": [],
      "env": {
        "SIGNOZ_URL": "<your-signoz-url>",
        "SIGNOZ_API_KEY": "<your-api-key>",
        "LOG_LEVEL": "info"
      }
    }
  }
}

<path-to-binary>: Absolute path to the signoz-mcp-server binary
<your-signoz-url>: Your SigNoz instance URL
<your-api-key>: The API key from Fetch your API key

Add to mcp_config.json (open via ... menu → MCP Servers → Manage MCP Servers → View raw config):

{
  "mcpServers": {
    "signoz": {
      "command": "<path-to-binary>/signoz-mcp-server",
      "args": [],
      "env": {
        "SIGNOZ_URL": "<your-signoz-url>",
        "SIGNOZ_API_KEY": "<your-api-key>",
        "LOG_LEVEL": "info"
      }
    }
  }
}

<path-to-binary>: Absolute path to the signoz-mcp-server binary
<your-signoz-url>: Your SigNoz instance URL
<your-api-key>: The API key from Fetch your API key

Configuration Reference

Environment variables for the self-hosted MCP server. SigNoz Cloud users do not need to set these.

Variable	Description	Default
`SIGNOZ_URL`	URL of your SigNoz instance	(required for stdio; optional for http with OAuth)
`SIGNOZ_API_KEY`	API key for authenticating with SigNoz	(required for stdio; optional for http with OAuth)
`TRANSPORT_MODE`	Transport protocol: `stdio` or `http`	`stdio`
`MCP_SERVER_HOST`	Host/interface for the HTTP server. Empty listens on all interfaces; set `127.0.0.1` for loopback-only access	(all interfaces)
`MCP_SERVER_PORT`	Port for HTTP server (when `TRANSPORT_MODE=http`)	`8000`
`LOG_LEVEL`	Logging verbosity: `debug`, `info`, `warn`, `error`	`info`
`CLIENT_CACHE_SIZE`	Maximum cached tenant clients in multi-tenant HTTP mode	`256`
`CLIENT_CACHE_TTL_MINUTES`	Tenant-client cache lifetime in minutes	`30`
`SIGNOZ_CUSTOM_HEADERS`	Extra HTTP headers added to every SigNoz API request, such as reverse-proxy auth headers. Format: `Key1:Value1,Key2:Value2`	(optional)
`SIGNOZ_DOCS_REFRESH_INTERVAL`	Refresh interval for the embedded docs sitemap used by `signoz_search_docs` / `signoz_fetch_doc` (Go duration)	`6h`
`SIGNOZ_DOCS_FULL_REFRESH_INTERVAL`	Full refresh interval for the embedded docs corpus (Go duration)	`24h`
`OAUTH_ENABLED`	Enable OAuth 2.1 authentication (`true`/`false`)	`false`
`OAUTH_TOKEN_SECRET`	Encryption key for OAuth tokens (min 32 bytes)	(required when `OAUTH_ENABLED=true`)
`OAUTH_ISSUER_URL`	Public URL of this MCP server	(required when `OAUTH_ENABLED=true`)
`OAUTH_ACCESS_TOKEN_TTL_MINUTES`	Access token lifetime in minutes	`60`
`OAUTH_REFRESH_TOKEN_TTL_MINUTES`	Refresh token lifetime in minutes	`43200` (30d)
`OAUTH_AUTH_CODE_TTL_SECONDS`	Authorization code lifetime in seconds	`600` (10min)

Validate

After connecting, verify the server is working:

Open your AI assistant.
Ask: "List all alerts" or "Show me all available services".
The assistant should return structured results from your SigNoz instance.

Available Tools

The MCP server exposes the following tools to your AI assistant:

Some tools use newer SigNoz APIs. Use SigNoz v0.131.0 or later for signoz_check_metric_usage, v0.120.0 or later for alert-rule list/get/create/update/delete tools, and v0.118.0 or later for signoz_get_alert_history. Notification-channel tools also use newer channels APIs. Older SigNoz deployments may return HTTP 404 from affected tools.

Tool	Description
`signoz_list_metrics`	Discover active metric names and catalog metadata such as type, temporality, and unit
`signoz_query_metrics`	Query a known metric for values, trends, breakdowns, or formulas with metric-aware defaults
`signoz_get_top_metrics`	Return top 100 metrics ranked by ingested sample volume with 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, or inhibited Alertmanager alert instances
`signoz_list_alert_rules`	List configured alert rules, including inactive or disabled rules
`signoz_get_alert`	Get an alert rule definition by ID
`signoz_get_alert_history`	Get a rule's firing and state-transition history (cursor-paginated)
`signoz_create_alert`	Create an alert rule using v2 schema validation
`signoz_update_alert`	Update an existing alert rule
`signoz_delete_alert`	Delete an alert rule
`signoz_list_dashboards`	List all dashboards with summaries
`signoz_get_dashboard`	Get full dashboard configuration
`signoz_create_dashboard`	Create a new dashboard
`signoz_update_dashboard`	Update an existing dashboard
`signoz_delete_dashboard`	Delete a dashboard by UUID
`signoz_list_dashboard_templates`	List the bundled SigNoz dashboard template catalog so the model can pick one
`signoz_import_dashboard`	Create a dashboard from a curated SigNoz dashboard template by path
`signoz_list_services`	List APM services with trace activity in a time range
`signoz_get_service_top_operations`	Get top operations for a service
`signoz_list_views`	List saved Explorer views for traces, logs, or metrics
`signoz_get_view`	Get a saved Explorer view by UUID
`signoz_create_view`	Create a saved Explorer view
`signoz_update_view`	Replace an existing saved Explorer view
`signoz_delete_view`	Delete a saved Explorer view
`signoz_aggregate_logs`	Aggregate logs (count, avg, p99, etc.) with grouping
`signoz_search_logs`	Search logs with flexible filtering
`signoz_aggregate_traces`	Aggregate trace statistics with grouping
`signoz_search_traces`	Search traces with flexible filtering
`signoz_get_trace_details`	Get full trace with all spans
`signoz_execute_builder_query`	Run Query Builder v5 requests the dedicated tools cannot express, including multi-query requests, formulas, PromQL, and ClickHouse SQL
`signoz_search_docs`	Search official SigNoz docs for product, setup, instrumentation, config, API, deployment, or troubleshooting questions
`signoz_fetch_doc`	Fetch full markdown for one official SigNoz docs page or heading
`signoz_list_notification_channels`	List notification channels
`signoz_get_notification_channel`	Get a single notification channel by ID
`signoz_create_notification_channel`	Create a notification channel and send a test notification
`signoz_update_notification_channel`	Update a notification channel and send a test notification
`signoz_delete_notification_channel`	Delete a notification channel by ID

The server also exposes read-only MCP resources (signoz://... URIs) with schemas, query-builder guides, and payload examples that AI assistants read before composing alert, dashboard, and view payloads.

For detailed parameter reference and the full resource list, see the GitHub repository README.

Troubleshooting

Tools not appearing in the AI client

Verify the binary path is correct and the file is executable (self-hosted only).
Set LOG_LEVEL=debug for detailed server logs.

Authentication errors

For SigNoz Cloud: ensure you are using the correct region in the MCP URL.
Confirm your API key is valid and has not expired.
For self-hosted HTTP mode where the client sends the key, use the SIGNOZ-API-KEY: <your-api-key> header.

SigNoz Cloud connection issues

Verify the region in the URL matches your account (https://mcp.<region>.signoz.cloud/mcp).
Check your network can reach mcp.<region>.signoz.cloud.
Make sure you completed the authentication flow when prompted.

Server not starting (self-hosted HTTP mode)

Ensure port 8000 is not already in use.
Check that TRANSPORT_MODE=http is set.
Review server logs for startup errors.

Connect to SigNoz's MCP server

Install in one click

Manual Configuration

Install in one click

Manual Configuration

Configure

Configure

Configure

Configure

Configure

Configure

Authenticate from your client

Header-Based Authentication

Fetch your API key

Install the MCP server

Configure your MCP client

Configuration Reference

Validate

Available Tools

Troubleshooting

Tools not appearing in the AI client

Authentication errors

SigNoz Cloud connection issues

Server not starting (self-hosted HTTP mode)

Was this page helpful?

Is this page helpful?