MCP server that decodes minified production stack traces back to original TypeScript source files, lines, and columns using source maps.
Most file and storage access work still happens through a UI a human drives. Sourcemap MCP server moves it into the conversation instead. MCP server that decodes minified production stack traces back to original TypeScript source files, lines, and columns using source maps.
The server publishes 3 tools. What each one is for:
retrace_stack — Decode a minified stack trace back to original TypeScript source locations. Pass the raw stack trace and the directory containing your .js.map filesretrieve_code_context — Show the original source lines surrounding a mapped error location — with line numbers and a column pointeraudit_sourcemap_match — Validate that .map files in your dist directory are present and point to source files that actually exist on disk. Catches stale or missing mapsSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Sourcemap's toolset — retrace_stack, retrieve_code_context, audit_sourcemap_match — is a fair guide to whether it matches your workflow. It is maintained by vola-trebla; 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 |
|---|---|
| retrace_stack | Decode a minified stack trace back to original TypeScript source locations. Pass the raw stack trace and the directory containing your .js.map files. |
| retrieve_code_context | Show the original source lines surrounding a mapped error location — with line numbers and a column pointer. |
| audit_sourcemap_match | Validate that .map files in your dist directory are present and point to source files that actually exist on disk. Catches stale or missing maps before deployment. |
{
"mcpServers": {
"sourcemap-retrace": {
"command": "npx",
"args": ["-y", "sourcemap-retrace-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.