A side-by-side look at the Simpletel and MCP Trace 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 MCP Trace for monitoring. 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.list_runs, run_summary, span_tree.Rows where the two servers differ are marked.
| Spec | S Simpletel | M MCP Trace |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 45/100 · Fair | 47/100 · Fair |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | SIMPLETEL_ENDPOINTSIMPLETEL_TEAMSIMPLETEL_ADMIN_TOKENSIMPLETEL_TOKENSIMPLETEL_CONFIG | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | 12 |
| Full listing | View Simpletel | View MCP Trace |
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).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.Paste 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.
No confirmed install command for MCP Trace yet — follow the setup steps linked from its listing page rather than a guessed package name.