Source_map_parser

Created By
MasonChowa year ago
Overview

what is Source Map Parser?

Source Map Parser is a WebAssembly-based tool that helps developers map JavaScript error stack traces back to the original source code, making it easier to locate and fix issues.

how to use Source Map Parser?

To use Source Map Parser, you can integrate it into your project using the command npx -y source-map-parser-mcp@latest and follow the provided usage guide to parse stack traces.

key features of Source Map Parser?

  • Stack Trace Parsing: Maps error stack traces to the original source code based on line and column numbers.
  • Batch Parsing: Allows parsing of multiple stack traces at once, returning results in a batch.
  • Context Extraction: Extracts context lines around the error to provide better insight into the error's environment.

use cases of Source Map Parser?

  1. Debugging JavaScript applications by tracing errors back to their source.
  2. Enhancing error reporting tools with detailed stack trace information.
  3. Assisting developers in understanding complex error scenarios in production environments.

FAQ from Source Map Parser?

  • Can Source Map Parser handle all JavaScript errors?

Yes! It can parse stack traces for any JavaScript error as long as the corresponding Source Map is available.

  • Is Source Map Parser easy to integrate?

Yes! It can be easily integrated into any JavaScript project using npm.

  • What if the Source Map file is not accessible?

Ensure that the URL provided for the Source Map file is correct and accessible to avoid parsing errors.

Server Config

{
  "mcpServers": {
    "source_map_parser": {
      "command": "npx",
      "args": [
        "-y",
        "source-map-parser-mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MasonChow
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago