Parse JavaScript error stack traces back to original source code using source maps
Parse JavaScript error stack traces back to original source code using source maps. That is what the source mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
This project implements a WebAssembly-based Source Map parser that can map JavaScript error stack traces back to source code and extract relevant context information. Developers can easily map JavaScript error stack traces back to source code for quick problem identification and resolution. This documentation aims to help developers better understand and use this tool.
source-map-parser-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 4 tools. What each one is for:
operating_guide — Get usage instructions for the MCP service. Provides information on how to use the MCP service through chat interactionparse_stack — Parse stack information by providing stack traces and Source Map addresseslookup_context — Look up original source code context for a specific line and column position in compiled/minified codeunpack_sources — Extract all source files and their content from a source mapConfiguration is passed through the environment: SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE, SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Source's toolset — operating_guide, parse_stack, lookup_context and 1 more — is a fair guide to whether it matches your workflow. It is maintained by MasonChow; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| operating_guide | Get usage instructions for the MCP service. Provides information on how to use the MCP service through chat interaction. |
| parse_stack | Parse stack information by providing stack traces and Source Map addresses. |
| lookup_context | Look up original source code context for a specific line and column position in compiled/minified code. |
| unpack_sources | Extract all source files and their content from a source map. |
{
"mcpServers": {
"source-map-parser": {
"command": "npx",
"args": ["-y", "source-map-parser-mcp"],
"env": {
"SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE": "your-value",
"SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE | Configuration value read at startup. | Optional |
| SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.