A side-by-side look at the MCP Trace and Scrivener MCP 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 Scrivener MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
list_runs, run_summary, span_tree.Rows where the two servers differ are marked.
| Spec | M MCP Trace | |
|---|---|---|
| Category | Monitoring | Knowledge & Memory |
| Quality signal | 47/100 · Fair | 61/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 67 |
| Directory activity | 0 views 0 installs 0 upvotes | 18 views 12 installs 6 upvotes |
| Tools | 12 | Not listed |
| Full listing | View MCP Trace | View Scrivener MCP |
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.No tool names declared yet. Check the project README from the listing page.
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 MCP Trace yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}