A side-by-side look at the MCP Trace and SigNoz MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Trace for monitoring work; choose SigNoz MCP Server for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
list_runs, run_summary, span_treeSIGNOZ_URL, SIGNOZ_API_KEY, LOG_LEVEL, TRANSPORT_MODE, MCP_SERVER_PORT, MCP_SERVER_HOST.signoz_get_org_overview, signoz_list_metrics, signoz_query_metrics.Rows where the two servers differ are marked.
| Spec | M MCP Trace | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 47/100 · Fair | 57/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | SIGNOZ_URLSIGNOZ_API_KEYLOG_LEVELTRANSPORT_MODEMCP_SERVER_PORTMCP_SERVER_HOST |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 125 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 12 | 43 |
| Full listing | View MCP Trace | View SigNoz MCP Server |
list_runsStarting out — recent runs with task, model, duration, cost, decision countsrun_summaryOne run at a glance (accepts trace-id prefix)span_tree"What did the agent actually do?" — nested shape of the runslowest_spans"Why was it slow?" — top-k spans by durationapproval_logHITL audit — every approve/deny/**edit**, who decided, and *the rationale*token_usageCost questions — aggregated across runs or per-runsearch_spansFind spans by tool name, file path, "denied", …failure_reportFind actionable, bounded, redacted errors and failed tool calls.tool_statsRank tools by volume, error rate, denials, and latency.security_auditAudit caller identity, tenant, server provenance, risk, and approval evidence.recent_activityPoll new spans with a cursor while a run is active.compare_runsCompare selected traces for regressions across models or versions.signoz_get_org_overviewGet the current status and overall posture of the SigNoz deployment, with typed projections plus `sourceStats` containing every reported stats fieldsignoz_list_metricsDiscover active metric names and catalog metadatasignoz_query_metricsQuery known metrics for values, trends, breakdowns, or formulassignoz_get_top_metricsReturn top 100 metrics ranked by ingested sample volume with pre-computed percentages for cost and volume analysissignoz_check_metric_usageGiven a list of metric names (up to 50 per call), return which dashboards and alerts reference each onesignoz_check_metric_cardinalityReturn label/attribute keys for a single metric with cardinality counts and sample values, sorted highest-cardinality firstsignoz_get_field_keysDiscover available field keys for metrics, traces, or logssignoz_get_field_valuesGet possible values for a field keysignoz_list_alertsList firing/silenced/inhibited Alertmanager alert *instances* (not rule definitions)signoz_list_alert_rulesList configured alert-rule summaries, including inactive/OK and disabled rulessignoz_get_alertGet one alert rule's full definition by `idsignoz_get_alert_historyGet one rule's firing or state-transition historyPaste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
No confirmed install command for MCP Trace yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"signoz-mcp-server": {
"url": "https://your-public-mcp-url.com/mcp"
}
}
}