Skip to main content
Glama
Sign In
apitrace-mcp

apitrace-mcp

by phunkaeg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to apitrace-mcp

No user-submitted related servers found.

    Related Servers

    • erdgraph

      nickjoven
      A
      license
      B
      quality
      C
      maintenance
      Enables agents to explore a static RTTI, call, and cross-reference graph of a game executable, querying functions, classes, vtables, strings, globals and memory through search, disassembly, signature and SQL tools. It also supports a provenance-tracked naming lifecycle where labels are proposed with evidence, reviewed, and ported across game patches.
      18
      MIT

    • Universal Game Modder

      doritoman90000
      A
      license
      C
      quality
      B
      maintenance
      Enables an AI agent to auto-detect a game's engine (Unity, Unreal, Godot, Java, or native) from its files and then inspect, search, and patch the underlying binaries with in-process PE analysis, hex editing, pattern scanning, string extraction, checksums, diffing, and disassembly. Everything runs locally and offline with no cloud dependency or telemetry.
      100
      64 npm
      5
      MIT

    • RenderDoc MCP Fusion

      KallkaGo
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives MCP clients tools to inspect RenderDoc .rdc captures — listing and opening frames, querying draws, pipelines, shaders, bindings, textures, buffers and pixel history, reading GPU performance counters, and exporting buffer, texture, mesh, draw-call and Unity import packages. Multiple clients can share one local GUI or headless playback backend on Windows.
      1
      MIT

    • nsight-graphics-mcp

      scarletfantasy
      A
      license
      A
      quality
      D
      maintenance
      MCP server for reading, filtering, and analyzing NVIDIA Nsight Graphics captures via ngfx-replay, exposing tools for capture inspection, GPU Trace profiling, and replay analysis.
      26
      2
      MIT

    • ReversePort

      laaielichter
      A
      license
      Not graded
      quality
      B
      maintenance
      Reverse engineer and port software and games from any coding agent: identify engines and builds, read Godot packs, Unity IL2CPP, .NET and native binaries (decompiling through Ghidra, IDA or Hopper), and port between Godot, Unity, Unreal and three.js with parity checks. Runs locally, only for software you own or may legally analyse.
      1,917 npm
      20
      MIT

    • x64dbg-MCP

      cipherwire
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects AI models and autonomous agents to the x64dbg debugger through the Model Context Protocol, exposing 234 tools for live execution control, register and memory inspection, disassembly, breakpoints, thread scheduling, console I/O, and PE analysis. It also parses saved .trace32/.trace64 trace files offline for instruction search, register lookups, and timeline navigation without x64dbg running.
      1
      GPL 3.0
    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

    B3.4/5.0

    Scored across 32 tools

    Disambiguation5/5

    Every tool targets a distinct operation: capture, replay, status, session listing, call dumping, call searching, histogramming, frame analysis, matrix finding, state dumps, and diffing are all cleanly separated. Even close neighbors like dump_calls/get_calls and diff_traces/diff_state are explicitly differentiated by their descriptions.

    Naming Consistency4/5

    The set predominantly follows snake_case verb_noun naming, e.g., list_traces, replay_trace, trace_stop, dump_state, extract_blobs, trim_trace. Minor deviations like apitrace_status, call_histogram, frame_summary, leak_report, and sed_trace break the pattern but remain readable and predictable.

    Tool Count2/5

    32 tools is a heavy surface for an agent to reason over, and several could plausibly be consolidated, such as trace_status/list_sessions, list_frames/frame_summary, and trim_trace/gltrim_trace. While the tool count reflects the breadth of apitrace, it exceeds the practical range for a coherent MCP server.

    Completeness5/5

    The toolset covers the full apitrace workflow: preflight checks, capture methods, session control, replay, inspection, frame and matrix analysis, shader/blob extraction, state dumping, trimming, compression, leak detection, and diffing. There are no obvious dead ends—install_wrapper has uninstall_wrapper, trace_launch has trace_stop, and replay_trace has trace_status.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Resources