Schema | sourcemap-retrace-mcp

sourcemap-retrace-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
retrace_stackA	Decode a minified production stack trace back to original TypeScript source files, lines, and columns.
retrieve_code_contextA	Show the original source code lines surrounding a mapped error location.
audit_sourcemap_matchB	Validate that .map files in a dist directory align with their compiled .js counterparts.
verify_debug_id_integrityB	Validate that a minified production bundle matches its source map using embedded Debug IDs.
normalize_bundler_pathsA	Resolve dynamic bundle references (like webpack://, ng://, or Vite /@fs/ paths) to raw files.
ingest_telemetry_payloadA	Directly ingest Sentry, Bugsnag, or Datadog crash dumps and return fully retraced stack frames.
surface_async_causalityA	Detect and trace across async boundaries (e.g. await, processTicksAndMicrotasks) to locate scheduling origins.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vola-trebla/sourcemap-retrace-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server