renderdoc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RENDERDOC_MODULE_PATH | Yes | The directory containing the RenderDoc Python module (renderdoc.pyd on Windows, librenderdoc.so on Linux) |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connect_to_gui_captureC | 打开 RenderDoc GUI 当前加载的 rdc。 |
| open_captureC | 按路径打开 rdc。 |
| close_captureC | 关闭当前 capture。 |
| export_mesh_stage_dataC | 导出一个 mesh stage。常用 stage 是 vsin 和 vsout。 |
| export_event_texturesC | 导出一个 draw 绑定的纹理。 |
| export_draw_bundleC | 导出 VSIn、VSOut、纹理和 manifest。 |
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 6 tools
Each tool has a clearly distinct purpose: closing, connecting to GUI, opening, and exporting different types of data. No overlapping functionality.
All tool names follow a consistent verb_noun pattern using snake_case, such as close_capture, open_capture, and export_event_textures.
With 6 tools, the surface is well-scoped for the domain of capture management and export, neither too few nor too many.
Covers core operations: opening, closing, connecting to GUI, and exporting various artifacts. Minor gaps like listing captures exist but do not severely hinder workflows.