mcp-server-signoz
Provides a Go-based Model Context Protocol (MCP) server (STDIO transport) that exposes SigNoz observability data access as MCP tools. It connects to a user’s SigNoz instance (URL plus optional API key), supporting queries for dashboards, services, APM metrics, and trace/log retrieval via ClickHouse SQL, as well as executing custom ClickHouse or SigNoz builder queries within time ranges.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
TLS is configurable and defaults to enabled; there is an option to skip certificate verification (which should be avoided). Upstream authentication is via SigNoz API key, but the MCP server’s own authorization model is not described (i.e., any MCP client that can access STDIO may query SigNoz). README claims input validation, built-in rate limiting, and that sensitive info is not exposed in errors, but it does not provide concrete details about SQL sanitization/guardrails for the custom query tools, which could be risky if untrusted agents/users can supply SQL.
⚡ Reliability
Best When
You want an MCP-compatible integration to query SigNoz observability data from tools like Claude Desktop/Cursor using STDIO.
Avoid When
You need a REST/HTTP API, webhooks, or cloud-hosted managed service rather than a local MCP server process; or you cannot restrict/validate query inputs when enabling custom SQL execution.
Use Cases
- • Use an AI/MCP client to inspect SigNoz dashboards and panel data
- • Retrieve APM metrics (request/error/latency/apdex) for a service over a time range
- • List instrumented services and explore what is deployed
- • Fetch traces or logs by issuing ClickHouse-based queries via MCP tools
- • Run custom ClickHouse SQL queries against SigNoz data (with time range support)
- • Assist troubleshooting by fetching observability data programmatically from an MCP client
Not For
- • Serving as a public multi-tenant API gateway without additional security controls
- • Performing write operations or state changes in SigNoz (appears to be read/query-focused)
- • Handling extremely large/long-running analytics without careful query limits and time bounds
- • Use where you cannot control/secure SQL inputs from an untrusted user/agent
Interface
Authentication
Authentication is described as optional depending on SigNoz configuration. No OAuth or fine-grained scope model is described for MCP access itself; MCP server appears to rely on the configured upstream SigNoz auth.
Pricing
Pricing for the package/service is not described; repository appears to be open source and self-hosted.
Agent Metadata
Known Gotchas
- ⚠ Custom ClickHouse/SQL execution tools can be expensive or slow; use strict time ranges and query limits to avoid timeouts.
- ⚠ If your SigNoz instance requires auth, missing/incorrect SIGNOZ_MCP_SIGNOZ_API_KEY will likely cause connectivity/auth errors.
- ⚠ TLS skip verification (SIGNOZ_MCP_SIGNOZ_TLS_SKIP_VERIFY) can reduce security; ensure it’s not enabled in production.
- ⚠ Tool outputs may depend on dashboard/service naming conventions; mismatches can lead to empty results or query failures.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server-signoz.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.