A side-by-side look at the Simpletel 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 Simpletel 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.
SIMPLETEL_ENDPOINT, SIMPLETEL_TEAM, SIMPLETEL_ADMIN_TOKEN, SIMPLETEL_TOKEN, SIMPLETEL_CONFIG.get_traces, get_trace, verify.SIGNOZ_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 | S Simpletel | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 45/100 · Fair | 57/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | SIMPLETEL_ENDPOINTSIMPLETEL_TEAMSIMPLETEL_ADMIN_TOKENSIMPLETEL_TOKENSIMPLETEL_CONFIG | 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 | 4 | 43 |
| Full listing | View Simpletel | View SigNoz MCP Server |
get_tracesLists this team's traces newest-first. The JSON document `simpletel get traces --format json` produces. Use it to find a failing or slow request.get_traceFetches one trace in full — spans, span events, and correlated log records. The JSON document `simpletel get trace <id> --format json` produces.verifyRuns the `simpletel verify` onboarding check: polls until `service` has a fresh trace carrying spans from a library instrumentation. Returns the rung report and the exit status (`0` verified, `1` deadline miss). A deadline miss is a completed check, not a tool error.usageShows the account's plan, month-to-date records, allowance, and spend cap. The JSON document `simpletel usage --format json` produces. Account-scoped (needs a logged-in user token).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 Simpletel 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"
}
}
}