sourcemap-retrace-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| retrace_stackA | Decode a minified production stack trace back to original TypeScript source files, lines, and columns. |
| retrieve_code_contextA | Show the original source code lines surrounding a mapped error location. |
| audit_sourcemap_matchB | Validate that .map files in a dist directory align with their compiled .js counterparts. |
| verify_debug_id_integrityB | Validate that a minified production bundle matches its source map using embedded Debug IDs. |
| normalize_bundler_pathsA | Resolve dynamic bundle references (like webpack://, ng://, or Vite /@fs/ paths) to raw files. |
| ingest_telemetry_payloadA | Directly ingest Sentry, Bugsnag, or Datadog crash dumps and return fully retraced stack frames. |
| surface_async_causalityA | Detect and trace across async boundaries (e.g. await, processTicksAndMicrotasks) to locate scheduling origins. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.