F
licenseNot graded
qualityC
maintenanceMCP server for RenderDoc that lets AI assistants analyze GPU frame captures, inspect draw calls, shaders, and render passes for graphics debugging and performance analysis.
-
renderdoc-mcp
by kenzo1024
Related Servers
Alternatives to renderdoc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceExposes RenderDoc capture analysis to AI clients via MCP, enabling offline analysis of .rdc files (action tree, pipeline state, textures, shaders) and GUI state interaction on Windows.2MIT
- AlicenseAqualityNot gradedmaintenanceEnables 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.12MIT
- FlicenseNot gradedqualityDmaintenanceEnables 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-
- AlicenseBqualityCmaintenanceAI-first WebGL 1/2 debugging MCP server that attaches to Chrome via CDP, enables frame capture and diagnostic analysis, and collaborates with Chrome DevTools MCP for agent-driven debugging workflows.395 npm1MIT
- AlicenseBqualityCmaintenanceEnables AI clients to analyze RenderDoc captures by browsing draw/dispatch events, inspecting pipeline state and shaders, and paginating vertex/constant buffer data.13MIT
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