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. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| renderdoc_check_available | Check if RenderDoc is available on the system. Returns availability status and installation info. |
| renderdoc_open_capture | Open an RDC capture file for analysis. Returns basic information about the capture including API type, frame count, and resource counts. |
| renderdoc_close_capture | Close the currently open RDC capture file and release resources. |
| renderdoc_get_capture_info | Get detailed information about the currently open capture including API, driver, and resource counts. |
| renderdoc_get_textures | Get a list of all textures in the capture with their properties (dimensions, format, mip levels, etc.). |
| renderdoc_get_buffers | Get a list of all buffers in the capture with their properties (size, type, etc.). |
| renderdoc_get_draw_calls | Get a list of all draw calls/events in the capture with their properties. |
| renderdoc_get_shader_info | Get detailed information about a specific shader including its reflection data. |
| renderdoc_get_pixel_data | Get pixel color data at a specific location in a texture. |
| renderdoc_get_texture_thumbnail | Get a base64 encoded thumbnail image of a texture. Useful for quickly visualizing texture contents. |
| renderdoc_analyze_draw_call | Perform detailed analysis of a specific draw call including input/output resources, shaders, and state. |
| renderdoc_search_resources | 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 | |