stacktrace-mcp
About
Simple JS Stacktrace MCP for getting the nearest error location from JS asset URL and let LLM checks if it matches anything with current codebase. Designed for non-sourcemap users.
Explore
- 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
1. Clone the repo
2. Run pnpm i for install
3. Run pnpm build for building the server
4. Add the local mcp server file path to your MCP-supported app (VSCode Copilot, etc):
// settings.json
"mcp": {
"servers": {
"stacktrace-mcp-server": {
"type": "stdio",
"command": "node",
"args": [
"<your-path-to>\/stacktrace-mcp\/dist\/mcp_server.cjs"
]
}
}
}
5. Make sure the mcp tool is already enabled
6. Copy your error stack trace to the prompt chat! That's it
Simple JS Stacktrace MCP for getting the nearest error location from JavaScript bundle URL
and lets an LLM checks if it matches anything in the current codebase.
> Designed for non-sourcemap users.
Getting started
1. Clone the repo
2. Run pnpm i for install
3. Run pnpm build for building the server
4. Add the local mcp server file path to your MCP-supported app (VSCode Copilot, etc):
// settings.json
"mcp": {
"servers": {
"stacktrace-mcp-server": {
"type": "stdio",
"command": "node",
"args": [
"<your-path-to>\/stacktrace-mcp\/dist\/mcp_server.cjs"
]
}
}
}
5. Make sure the mcp tool is already enabled
6. Copy your error stack trace to the prompt chat! That's it
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
