SigNoz MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 2 Nov 2026.
SigNoz MCP server: access metrics, traces, logs, alerts, and dashboards via AI assistants
What the code does
We read the source, 21 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
path = os.path.join(root, "internal", "handler", "tools", "schemas", f"dashboard_{name}.json")
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to SigNoz MCP Server
same job, measured the same wayMCP server for Dynatrace Managed to access logs, events, and metrics.
Full Datadog API access: monitors, logs, metrics, traces, dashboards, and observability tools
MCP server providing Prometheus metrics access and PromQL query execution for AI assistants
An MCP server giving access to Grafana dashboards, data and more.
Access New Relic observability data through MCP - query metrics, logs, traces, entities, and more
Manage uptime monitors and incidents and search logs, metrics and traces from an AI assistant.
Connect AI assistants to Xitoring monitoring: servers, uptime, incidents, metrics, SSL, and alerts.
Query OpenTelemetry logs, traces and metrics from a self-hosted OTLP dashboard
SigNoz MCP Server — questions
Answers built from our own checks of this server.