Parse JavaScript error stack traces back to original source code using source maps
Connect Runs on your machine
claude mcp add source-map-parser-mcp -e SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE=<SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE> -e SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE=<SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE> -- npx -y [email protected]
{
"mcpServers": {
"source-map-parser-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE": "<SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE>",
"SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE": "<SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE>"
}
}
}
}
{
"mcpServers": {
"source-map-parser-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE": "<SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE>",
"SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE": "<SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE>"
}
}
}
}
{
"servers": {
"source-map-parser-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE": "<SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE>",
"SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE": "<SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINEOptional | Context lines around error locations in source code |
SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZEOptional | Maximum memory cache size in MB for source maps |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 10 Sep 2025 |
| Last updated | 10 Sep 2025 |
| Registry name | io.github.MasonChow/source-map-parser-mcp |
More data and analytics servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
