Skip to main content
Glama
Sign In
stacktrace-mcp

stacktrace-mcp

by 0xmortuex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to stacktrace-mcp

No user-submitted related servers found.

    Related Servers

    • ticket-forge

      SanjoyDat1
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      MCP server that parses stack traces and logs to generate deduplicated issue drafts with severity, repro steps, and owner guesses.
      -

    • AgentSensor

      arif-js
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to observe real-time Node, Vite, Next.js, Storybook, TypeScript, and browser runtime errors from a wrapped dev server, source-mapped to exact file, line, and column with the log lines preceding each crash. It exposes MCP tools for listing open errors, fetching full stack details, and checking or marking fixes as resolved, all locally with no code changes.
      4
      28 npm
      MIT

    • crashdx-mcp

      r00tify
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents and humans to analyze Apple .ips crash reports, symbolicate them against dSYMs, and obtain evidence-cited ranked diagnoses as structured analysis.
      7
      MIT

    • Rust Minidump MCP

      bahamoth
      A
      license
      Not graded
      quality
      C
      maintenance
      Analyzes application crash dumps and extracts debug symbols, transforming Windows minidump files into readable stack traces and providing AI-powered crash analysis to help identify root causes and fix critical issues.
      8
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct action in a clear pipeline: parse a trace, fingerprint it, scan a file for traces, map frames to source, compare two traces, explain a named exception type, and redact text. The only near-neighbors (parse_trace vs explain_exception, redact_trace vs the per-tool redact flag) are clearly separated by input type and scope, so misselection is unlikely.

    Naming Consistency4/5

    All names are snake_case and almost all follow a verb_noun pattern (parse_trace, compare_traces, map_to_code, redact_trace, find_traces_in_file). The lone outlier is 'fingerprint', which is a bare verb with no object, a minor deviation but still unambiguous.

    Tool Count5/5

    Seven tools is well within the ideal 3-15 range and each one covers a distinct step in a trace-triage workflow with no filler or redundancy. Nothing feels padded or missing at the count level.

    Completeness4/5

    The surface covers the full workflow: parse, stable identity via fingerprint, batch scanning of logs, source mapping, comparison, per-exception guidance, and sanitization. Minor gaps remain, such as no direct way to extract/normalize a single trace out of an arbitrary file path or to persist results, but agents can work around these with parse_trace and find_traces_in_file.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources