RenderDoc MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONPATH | No | Path to the RenderDoc Python module. To use the native Python API (recommended), set this to include the path to the RenderDoc plugins/python directory. If not set, the server will fall back to using the renderdoccmd command line tool. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| renderdoc_check_availableA | Check if RenderDoc is available on the system. Returns availability status and installation info. |
| renderdoc_open_captureA | Open an RDC capture file for analysis. Returns basic information about the capture including API type, frame count, and resource counts. |
| renderdoc_close_captureA | Close the currently open RDC capture file and release resources. |
| renderdoc_get_capture_infoB | Get detailed information about the currently open capture including API, driver, and resource counts. |
| renderdoc_get_texturesA | Get a list of all textures in the capture with their properties (dimensions, format, mip levels, etc.). |
| renderdoc_get_buffersB | Get a list of all buffers in the capture with their properties (size, type, etc.). |
| renderdoc_get_draw_callsB | Get a list of all draw calls/events in the capture with their properties. |
| renderdoc_get_shader_infoC | Get detailed information about a specific shader including its reflection data. |
| renderdoc_get_pixel_dataC | Get pixel color data at a specific location in a texture. |
| renderdoc_get_texture_thumbnailA | Get a base64 encoded thumbnail image of a texture. Useful for quickly visualizing texture contents. |
| renderdoc_analyze_draw_callC | Perform detailed analysis of a specific draw call including input/output resources, shaders, and state. |
| renderdoc_search_resourcesC | Search for resources (textures, buffers, shaders) by name pattern. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose targeting specific aspects of RenderDoc capture analysis, such as checking availability, opening/closing captures, retrieving lists of resources, analyzing draw calls, or fetching specific data like pixel colors or thumbnails. There is no significant overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent 'renderdoc_verb_noun' pattern with snake_case, such as 'renderdoc_open_capture' and 'renderdoc_get_textures'. This uniformity enhances readability and predictability, allowing agents to easily infer tool purposes from their names.
With 12 tools, the server is well-scoped for analyzing graphics captures, covering core operations like capture management, resource listing, detailed analysis, and data retrieval. Each tool serves a specific and necessary function without redundancy, making the count appropriate for the domain.
The toolset provides comprehensive coverage for capture analysis, including opening/closing captures, retrieving resource lists, analyzing draw calls and shaders, and accessing pixel data. A minor gap exists in operations like modifying captures or exporting data, but core analysis workflows are fully supported, allowing agents to perform most essential tasks.