Source Map Parser Mcp
Let your agent turn minified production stack traces into real file names and line numbers during incident triage.
Overview
source-map-parser-mcp is a MCP server for the Operate phase that maps JavaScript stack traces to original source locations via source maps.
What is this MCP server?
- Parses JavaScript error stack traces to original sources using source maps (v1.3.2)
- stdio MCP transport via npm package source-map-parser-mcp
- Configurable context lines via SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE
- In-memory source map cache cap via SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE (MB)
- Bridges production/minified errors to repo paths agents can open and patch
- Server version 1.3.2
- npm identifier source-map-parser-mcp
- 2 optional tuning environment variables (context lines, cache MB)
Community signal: 2 GitHub stars.
What problem does it solve?
Production errors point at minified bundles so your agent cannot find the real line to fix without manual source-map detective work.
Who is it for?
Solo builders shipping Vite, Webpack, or Next bundles who debug prod JS errors inside Claude Code or Cursor.
Skip if: Backend-only stacks with no browser bundles or teams without source maps published alongside builds.
What do I get? / Deliverables
After install, stack traces from the agent become actionable paths and context in your original TypeScript or JavaScript sources.
- Original file/line mapping from JS stack strings
- Configurable source context around error locations
- Cached source map loading for repeated parses
Recommended MCP Servers
Journey fit
Source-map resolution matters after ship when users hit bundled JS errors—you need operate-phase debugging, not greenfield coding. Stack trace parsing is error localization: mapping reported frames back to authored source under pressure.
How it compares
Source-map stack resolver MCP, not a full error monitoring or session replay product.
Common Questions / FAQ
Who is source-map-parser-mcp for?
Frontend-heavy indie devs and agents that need to decode minified stack traces during bugs and post-launch incidents.
When should I use source-map-parser-mcp?
When operate-phase errors arrive from minified assets and you want the agent to jump straight to the correct source file and lines.
How do I add source-map-parser-mcp to my agent?
Add the source-map-parser-mcp npm package (v1.3.2) as a stdio MCP server in your client config; optionally set SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE and SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE.