Skip to main content
Glama
halby24

RenderDoc MCP Server

by halby24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to RenderDoc MCP Server

No user-submitted related servers found.

    Related Servers

    • RenderDoc MCP Server

      ZylNice
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to access RenderDoc capture data and assist with graphics debugging by retrieving draw calls, shader information, buffers, textures, and pipeline state.
      15
      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.
      164
      -

    • RenderDoc MCP

      LifeSugar
      A
      license
      B
      quality
      C
      maintenance
      Enables AI clients to analyze RenderDoc captures by browsing draw/dispatch events, inspecting pipeline state and shaders, and paginating vertex/constant buffer data.
      13
      MIT
    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 15 tools

    Disambiguation5/5

    Every tool serves a distinct purpose with clearly defined search criteria or actions. For example, find_draws_by_resource, find_draws_by_shader, and find_draws_by_texture are all differentiated by the search parameter, and get_draw_calls vs get_draw_call_details separate listing from details.

    Naming Consistency4/5

    Most tools follow the verb_noun pattern (e.g., get_draw_calls, list_captures, open_capture), but there is minor inconsistency: 'find_draws_by_resource' vs 'get_draw_calls' (different verbs), and 'get_action_timings' vs 'get_draw_call_details' (different nouns for similar concepts).

    Tool Count4/5

    15 tools is appropriate for a graphics debugger MCP server, covering capture management, draw call queries, resource inspection, pipeline state, and timing. Slightly more than minimal but well-scoped.

    Completeness4/5

    The tool set covers the main inspection workflow: open capture, list actions, get details, check pipeline state, shaders, buffers, textures, and timings. Missing features like capturing a frame or stepping through events are expected external to MCP.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources