Server data from the Official MCP Registry
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
Set these up before or after installing:
Environment variable: SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE
Environment variable: SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-masonchow-source-map-parser-mcp": {
"env": {
"SOURCE_MAP_PARSER_CONTEXT_OFFSET_LINE": "your-source-map-parser-context-offset-line-here",
"SOURCE_MAP_PARSER_RESOURCE_CACHE_MAX_SIZE": "your-source-map-parser-resource-cache-max-size-here"
},
"args": [
"-y",
"source-map-parser-mcp"
],
"command": "npx"
}
}
}Valid MCP server (2 strong, 3 medium validity signals). 3 known CVEs in dependencies (0 critical, 3 high severity) Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
Scanned 3 files · 4 findings
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Be the first to review this server!