MCP Trace vs Trace Forge
A side-by-side look at the MCP Trace and Trace Forge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MCP TraceMonitoringQuery OpenTelemetry traces from agent runs through MCP.47FairAuth: no auth requiredVerdict: choose MCP Trace for monitoring work; choose Trace Forge for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
MChoose MCP Trace when
- You need dedicated capabilities in the Monitoring domain.
- Its auth model fits you: No auth required.
- You want tools like
list_runs, run_summary, span_tree.
Choose Trace Forge when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M MCP Trace | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 47/100 · Fair | 37/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | 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 | 12 | Not listed |
| Full listing | View MCP Trace | View Trace Forge |
Tools & capabilities
MCP Trace tools 12
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.
Trace Forge tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
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.
MCP Trace
No confirmed install command for MCP Trace yet — follow the setup steps linked from its listing page rather than a guessed package name.
Trace Forge
{
"mcpServers": {
"trace-forge": {
"command": "npx",
"args": [
"-y",
"trace-forge-mcp"
]
}
}
}
Frequently asked questions
MCP Trace is categorized under Monitoring and uses an install path we have not confirmed yet. Trace Forge belongs to Monitoring and uses a local stdio subprocess. Pick MCP Trace for monitoring work and Trace Forge for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. MCP Trace has no confirmed install command yet — follow its own setup instructions.
MCP Trace is listed as free. Auth: no auth required. Trace Forge has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-trace and trace-forge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Trace has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Trace Forge has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
