stacktrace-mcp

What is stacktrace-mcp?

stacktrace-mcp is a simple MCP server that provides the nearest error location from a JavaScript bundle URL and lets an LLM check if it matches anything in the current codebase. It is designed for users who do not have sourcemaps.

How to use stacktrace-mcp?

Clone the repository, install dependencies with pnpm i, build with pnpm build, then add the local MCP server file path to your MCP-supported application (e.g., VSCode Copilot) using the provided JSON configuration in settings.json. After enabling the MCP tool, paste an error stack trace into the prompt chat to start.

Key features of stacktrace-mcp

• Extracts the nearest error location from a JS bundle URL
• Lets an LLM match the error to the current codebase
• Works without sourcemaps
• Simple setup with a local file path
• Supports MCP‑compatible apps like VSCode Copilot

Use cases of stacktrace-mcp

• Debugging minified or bundled JavaScript errors in production
• Enabling an LLM to provide context‑specific fixes by matching stack traces to local source code
• Assisting developers who cannot generate or access sourcemaps
• Integrating error analysis into AI‑powered coding assistants

FAQ from stacktrace-mcp

What runtime does stacktrace-mcp require?

It requires Node.js and uses the pnpm package manager for installation and building.

How do I configure stacktrace-mcp in my editor?

Add the provided JSON block to your MCP settings (e.g., VSCode's settings.json) with the correct path to dist/mcp_server.cjs.

Can I use stacktrace-mcp with sourcemaps?

The tool is explicitly designed for non-sourcemap users; it expects a bundle URL and source files, not sourcemaps.

What transport does stacktrace-mcp use?

It uses stdio transport, configured via the "type": "stdio" field in the MCP server settings.

Where does the error data live?

Error stack traces are provided by the user in the chat prompt; the server does not store or transmit data externally.

Is authentication required?

No authentication is mentioned; the server runs locally on stdio and no credentials are needed.