Skip to main content
Glama
Sign In
renderdoc-mcp

renderdoc-mcp

by kenzo1024
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to renderdoc-mcp

No user-submitted related servers found.

    Related Servers

    • RenderDoc MCP Fusion

      KallkaGo
      A
      license
      Not graded
      quality
      B
      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

    • RenderDoc MCP Server

      Hengle
      A
      license
      A
      quality
      Not graded
      maintenance
      Enables AI assistants to analyze and inspect RenderDoc capture files, providing tools to examine draw calls, textures, buffers, and shader information. It allows developers to perform graphics debugging and resource analysis through natural language interactions.
      12
      MIT

    • renderdoc-mcp

      Linkingooo
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to analyze RenderDoc GPU frame captures for graphics debugging and performance analysis through a headless Python API. It provides a comprehensive suite of tools for inspecting pipeline states, shader bindings, and exporting frame resources like textures and meshes.
      181
      -
    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.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: closing, connecting to GUI, opening, and exporting different types of data. No overlapping functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as close_capture, open_capture, and export_event_textures.

    Tool Count5/5

    With 6 tools, the surface is well-scoped for the domain of capture management and export, neither too few nor too many.

    Completeness4/5

    Covers core operations: opening, closing, connecting to GUI, and exporting various artifacts. Minor gaps like listing captures exist but do not severely hinder workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources