RenderDoc MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| healthA | Check gateway limits and whether the configured replay backend is available. |
| launch_programC | Launch and inject an allow-listed .exe through qrenderdoc/RenderDoc. |
| open_captureB | Open one allow-listed .rdc file and return a stable capture_id. |
| close_captureB | Close a capture session and release its replay resources. |
| get_capture_summaryB | Return metadata and warnings for an open capture session. |
| list_actionsC | List capture actions with filtering and bounded cursor pagination. |
| get_eventC | Get draw, dispatch, copy, marker, or present details for one event ID. |
| inspect_eventC | Inspect selected pipeline sections for an event in one serialized replay call. |
| get_pipeline_stateC | Read common pipeline state or one API-specific top-level state section. |
| get_shaderC | Read a bound shader's reflection, disassembly, source, or raw bytes in pages. |
| get_vertex_dataC | Page through every vertex/instance input and decoded attribute, including UVs. |
| list_constant_buffersC | List every shader-stage/block/array constant-buffer group with pagination. |
| get_constant_bufferC | Read decoded variables and a bounded raw-byte page for one constant-buffer group. |
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 13 tools
Most tools have clearly distinct purposes across lifecycle, metadata, and inspection. However, get_event, inspect_event, and get_pipeline_state all operate on event IDs and pipeline data, creating some boundary overlap that could cause misselection in an agent.
Nearly all tools follow a clean snake_case verb_noun pattern (open_capture, get_event, list_actions, get_constant_buffer). The lone 'health' deviates as a bare noun, but it is a widely recognized convention so the impact is minor.
13 tools is well-scoped for a graphics debugging/replay server, with each tool earning its place across session lifecycle, event inspection, and pipeline/shader data retrieval. No redundancy or bloat.
Covers the core lifecycle (launch, open, close) plus rich inspection of actions, events, pipeline state, shaders, vertex data, and constant buffers. Minor gaps exist for resource/texture inspection or capture export, but core workflows are well covered.