Skip to main content
Glama
MasonChow

Source Map Parser MCP Server

by MasonChow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

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.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
parse_stackA

Parse Error Stack Trace

This tool allows you to parse error stack traces by providing the following:

  • A downloadable source map URL.

  • The line and column numbers from the stack trace.

The tool will map the provided stack trace information to the corresponding source code location using the source map. It also supports fetching additional context lines around the error location for better debugging.

Parameters:

  • stacks: An array of stack trace objects, each containing:

    • line: The line number in the stack trace.

    • column: The column number in the stack trace.

    • sourceMapUrl: The URL of the source map file corresponding to the stack trace.

  • ctxOffset (optional): The number of additional context lines to include before and after the error location in the source code. Defaults to 5.

Returns:

  • A JSON object containing the parsed stack trace information, including the mapped source code location and context lines.

  • If parsing fails, an error message will be returned for the corresponding stack trace.

lookup_contextA

Lookup Source Code Context

This tool looks up original source code context for a specific line and column position in compiled/minified code.

Parameters:

  • line: The line number in the compiled code (1-based)

  • column: The column number in the compiled code

  • sourceMapUrl: The URL of the source map file

  • contextLines (optional): Number of context lines to include before and after the target line (default: 5)

Returns:

  • A JSON object containing the source code context snippet with file path, target line info, and surrounding context lines

  • Returns null if the position cannot be mapped

unpack_sourcesA

Unpack Source Map Sources

This tool extracts all source files and their content from a source map.

Parameters:

  • sourceMapUrl: The URL of the source map file to unpack

Returns:

  • A JSON object containing:

    • sources: Object with source file paths as keys and their content as values

    • sourceRoot: The source root path from the source map

    • file: The original file name

    • totalSources: Total number of source files found

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clear, distinct purpose: lookup_context maps a single position to source context, parse_stack processes multiple stack entries, and unpack_sources extracts all source files. There is no overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: lookup_context, parse_stack, unpack_sources. The naming is predictable and easy to understand.

Tool Count4/5

With 3 tools, the server is focused and each tool serves a core need in source map parsing. While the count is small, it is appropriate for the domain; adding a validation or metadata tool could be beneficial but not necessary.

Completeness4/5

The toolset covers the primary tasks: single position mapping, stack trace parsing, and source extraction. Minor gaps exist (e.g., no direct source map metadata or validation), but the core functionality is well-covered.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources