sourcemap-retrace-mcp
Related Servers
Alternatives to sourcemap-retrace-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables mapping JavaScript error stack traces back to original source code, extracting context information to help developers locate and fix issues.3102 npm2MIT
- AlicenseAqualityBmaintenanceEnables turning pasted or logged crash output from Python, Node, Java, Go, Rust, and .NET into compact root-cause reports, mapping frames onto project code, fingerprinting and comparing traces, explaining exceptions, and redacting secrets over MCP.7MIT

gn-tracing-mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables coding agents to read a replay link or a gn-tracing-*.zip package, surfacing console errors with source-mapped stacks, failed requests, and the user timeline.GPL 3.0- AlicenseBqualityBmaintenanceEnables local analysis of TypeScript/TSX codebases into versioned dependency graphs with reviewable source evidence, explicit architectural boundaries, C4 diagrams, and interactive HTML with PNG/SVG exports.61,723 npmMIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to observe real-time Node, Vite, Next.js, Storybook, TypeScript, and browser runtime errors from a wrapped dev server, source-mapped to exact file, line, and column with the log lines preceding each crash. It exposes MCP tools for listing open errors, fetching full stack details, and checking or marking fixes as resolved, all locally with no code changes.428 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP-compatible clients to analyze TypeScript code by finding method references, dependency imports, and React component trees.MIT
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes, but retrace_stack and ingest_telemetry_payload both produce retraced frames, and audit_sourcemap_match and verify_debug_id_integrity both validate sourcemap integrity, which could cause some confusion. However, descriptions clarify the differences well.
All tool names follow a consistent verb_noun pattern with underscores, e.g., retrace_stack, audit_sourcemap_match, surface_async_causality. The verbs are specific and the nouns clearly indicate the target, making the set predictable and readable.
With 7 tools, the server is well-scoped for sourcemap retracing and analysis. Each tool addresses a meaningful aspect of the workflow without excessive overlap or unnecessary bloat.
The tool set covers core retracing, context retrieval, validation, path normalization, telemetry ingestion, and async tracing. Minor gaps such as direct support for sourcemap generation or batch processing are not essential for the stated purpose, so the surface is largely complete.