What authentication is required?
An API key is optional; if your SigNoz instance requires one, obtain it from the SigNoz UI and set it via the `SIGNOZ_API_KEY` environment variable or `config.yaml`.
@DrDroidLab
基本情報
The Signoz MCP Server lets you connect developer tools like Cursor or Claude Desktop to your Signoz instance. It's an open-source project maintained by DrDroid (not affiliated with Signoz), and allows you to query logs, dashboards, metrics, and more — making observability data di
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"signoz": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"SIGNOZ_HOST",
"-e",
"SIGNOZ_API_KEY",
"-e",
"SIGNOZ_SSL_VERIFY",
"signoz-mcp-server",
"-t",
"stdio"
],
"env": {
"SIGNOZ_HOST": "https://your-signoz-instance.com",
"SIGNOZ_API_KEY": "your-signoz-api-key-here",
"SIGNOZ_SSL_VERIFY": "true"
}
}
}
}Verify connectivity to your Signoz instance and configuration.
List all available dashboards from Signoz.
Retrieve detailed information about a specific dashboard by its ID. This information contains the metadata of the dashboard, not the live panel data.
Fetch all panel data for a given dashboard by name and time range.
Retrieve standard APM metrics (request rate, error rate, latency, apdex, etc.) for a given service and time range.
Fetch all instrumented services from Signoz with optional time range filtering.
Execute custom Clickhouse SQL queries via the Signoz API with time range support.
Execute Signoz builder queries for custom metrics and aggregations with time range support.
Fetch traces or logs from SigNoz using ClickHouse SQL. Specify `data_type` ('traces' or 'logs'), time range, service name, and limit. Returns tabular results for traces or logs.
Signoz MCP Server is an MCP (Model Context Protocol) server that connects AI assistants like Claude Desktop or Cursor to a SigNoz observability instance. It provides a set of tools to query dashboards, APM metrics, services, traces, logs, and execute ClickHouse queries directly from the AI tool.
Install dependencies with uv sync, then run with uv run -m src.signoz_mcp_server.mcp_server. Alternatively, deploy using Docker Compose or Docker with environment variables. Configure via config.yaml or environment variables (SIGNOZ_HOST, SIGNOZ_API_KEY, etc.). Integrate with AI assistants using stdio mode or HTTP/SSE endpoint.
An API key is optional; if your SigNoz instance requires one, obtain it from the SigNoz UI and set it via the `SIGNOZ_API_KEY` environment variable or `config.yaml`.
Configuration is loaded in order: environment variables take precedence over the YAML file (`config.yaml`). Supported env vars include `SIGNOZ_HOST`, `SIGNOZ_API_KEY`, `SIGNOZ_SSL_VERIFY`, `MCP_SERVER_PORT`, and `MCP_SERVER_DEBUG`.
The server supports stdio mode (for local integration with MCP clients like Claude Desktop) and HTTP/SSE mode (for remote or containerized deployments, default port 8000).
Access the health check endpoint at `http://localhost:8000/health` (or your configured host). Returns a success response when running.
All data remains in your SigNoz instance; the server only passes queries and results between the AI assistant and SigNoz. No data is stored by the MCP server.

Routebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.
MCP server for industrial namespace validation — Sparkplug B linter, UNS convention checker, and a free AI-readiness diagnostic. No API key required.
Console, Backend and CLI to manage Capgo Instant update and Native build for Capacitor apps Build and upload to app store your mobile app

Local-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.

Multi-zone MCP server for GKE/EKS/AKS: Python tools from git, NeMo guardrails, SSO, autoscaling.
コメント