
Sourcemap Retrace Mcp
When your production app throws errors with stack traces pointing to minified JavaScript at column 47821, this server maps them back to the original TypeScript file, line, and column using source maps. It exposes three tools: retrace_stack decodes the full trace, retrieve_code_context shows the surrounding source lines with a column pointer, and audit_sourcemap_match validates that your dist directory's .map files are present and point to sources that actually exist. You point it at a stack trace and your dist folder, and it tells you which TypeScript file and line crashed instead of leaving you staring at obfuscated bundles. Useful when debugging production incidents or helping an agent understand what actually failed.
- tools
- 3
- transport
- STDIO
- last updated
- May 20, 2026
Tools
3 toolsPublic tool metadata for what this MCP can expose to an agent.
retrace_stackDecode a minified stack trace back to original TypeScript source locations.
Decode a minified stack trace back to original TypeScript source locations.
No parameter schema in public metadata yet.
retrieve_code_contextShow the original source lines surrounding a mapped error location, with line numbers and a column pointer.
Show the original source lines surrounding a mapped error location, with line numbers and a column pointer.
No parameter schema in public metadata yet.
audit_sourcemap_matchValidate that .map files in your dist directory are present and point to source files that actually exist on disk.
Validate that .map files in your dist directory are present and point to source files that actually exist on disk.
No parameter schema in public metadata yet.
Sponsors
Readme
🗺️ sourcemap-retrace-mcp
Your app crashed in production. The stack trace is useless. Your AI agent has no idea where the bug is.
MCP server that decodes minified production stack traces back to original TypeScript source files, lines, and columns — using source maps. Before your agent spends 20 minutes guessing at obfuscated code.
🤔 The problem
Your monitoring tool sends you this:
TypeError: Cannot read properties of undefined (reading 'userId')
at e.<anonymous> (main.a3f2c1.js:1:47821)
at h (vendor.d4e5f6.js:1:12045)
at processQueue (main.a3f2c1.js:1:89234)
You ask your agent to debug it. The agent reads main.a3f2c1.js. It's 40,000 characters of minified JavaScript. It has no idea what e.<anonymous> at column 47821 means.
sourcemap-retrace-mcp maps that back to:
Details
- Repository
- github.com/vola-trebla/sourcemap-retrace-mcp
- Package
sourcemap-retrace-mcp- Transport
- STDIO
- Registry
- MCP registry, active
More from vola-trebla
- Tailwind Context Resolver Mcp
- Tsconfig Inheritance Flattener Mcp
- V8 Cpu Profile Decoder Mcp
- Release Readiness Triage Mcp
- React Render Profile Mcp2
- Playwright Trace Decoder Mcp1
- Ast Impact Mapper Mcp
- Env Secret Exposure Analyzer Mcp
- Flakiness Knowledge Graph Mcp
- Ndjson Local Log Triage Mcp
- Playwright Network Chaos Mcp
- Playwright Spatial Layout Mcp