Skip to main content
Glama
RenderDoc MCP Server

RenderDoc MCP Server

by halby24

RenderDoc MCP Server

RenderDoc UI拡張機能として動作するMCPサーバー。AIアシスタントがRenderDocのキャプチャデータにアクセスし、グラフィックスデバッグを支援する。

アーキテクチャ

Claude/AI Client (stdio)
        │
        ▼
MCP Server Process (Python + FastMCP 2.0)
        │ File-based IPC (%TEMP%/renderdoc_mcp/)
        ▼
RenderDoc Process (Extension)

RenderDoc内蔵のPythonにはsocketモジュールがないため、ファイルベースのIPCで通信を行う。

Related MCP server: RenderDoc MCP Server

セットアップ

1. RenderDoc拡張機能のインストール

python scripts/install_extension.py

拡張機能は %APPDATA%\qrenderdoc\extensions\renderdoc_mcp_bridge にインストールされる。

2. RenderDocで拡張機能を有効化

  1. RenderDocを起動

  2. Tools > Manage Extensions

  3. "RenderDoc MCP Bridge" を有効化

3. MCPサーバーのインストール

uv tool install
uv tool update-shell  # PATHに追加

シェルを再起動すると renderdoc-mcp コマンドが使えるようになる。

Note: --editable を付けると、ソースコードの変更が即座に反映される(開発時に便利)。 安定版としてインストールする場合は uv tool install . を使用。

4. MCPクライアントの設定

Claude Desktop

claude_desktop_config.json に追加:

{
  "mcpServers": {
    "renderdoc": {
      "command": "renderdoc-mcp"
    }
  }
}

Claude Code

.mcp.json に追加:

{
  "mcpServers": {
    "renderdoc": {
      "command": "renderdoc-mcp"
    }
  }
}

使い方

  1. RenderDocを起動し、キャプチャファイル (.rdc) を開く

  2. MCPクライアント (Claude等) から RenderDoc のデータにアクセス

MCPツール一覧

ツール

説明

get_capture_status

キャプチャの読み込み状態を確認

get_draw_calls

ドローコール一覧を階層構造で取得

get_draw_call_details

特定のドローコールの詳細情報を取得

get_shader_info

シェーダーのソースコード・定数バッファの値を取得

get_buffer_contents

バッファの内容を取得 (Base64)

get_texture_info

テクスチャのメタデータを取得

get_texture_data

テクスチャのピクセルデータを取得 (Base64)

get_pipeline_state

パイプライン状態を取得

使用例

ドローコール一覧の取得

get_draw_calls(include_children=true)

シェーダー情報の取得

get_shader_info(event_id=123, stage="pixel")

パイプライン状態の取得

get_pipeline_state(event_id=123)

テクスチャデータの取得

# 2Dテクスチャのmip 0を取得
get_texture_data(resource_id="ResourceId::123")

# 特定のmipレベルを取得
get_texture_data(resource_id="ResourceId::123", mip=2)

# キューブマップの特定の面を取得 (0=X+, 1=X-, 2=Y+, 3=Y-, 4=Z+, 5=Z-)
get_texture_data(resource_id="ResourceId::456", slice=3)

# 3Dテクスチャの特定の深度スライスを取得
get_texture_data(resource_id="ResourceId::789", depth_slice=5)

バッファデータの部分取得

# バッファ全体を取得
get_buffer_contents(resource_id="ResourceId::123")

# オフセット256から512バイト取得
get_buffer_contents(resource_id="ResourceId::123", offset=256, length=512)

要件

  • Python 3.10+

  • uv

  • RenderDoc 1.20+

Note: 動作確認はWindows + DirectX 11環境でのみ行っています。 Linux/macOS + Vulkan/OpenGL環境でも動作する可能性がありますが、未検証です。

ライセンス

MIT

Available Tools

15 tools
find_draws_by_resourceA

Find all draw calls using a specific resource ID (exact match).

Args: resource_id: Resource ID to search for (e.g. "ResourceId::12345" or "12345")

Returns a list of matching draw calls with event IDs and match reasons. Searches shaders, SRVs, UAVs, render targets, and depth targets.

Inputs: resource_id (required). Returns: object

find_draws_by_shaderA

Find all draw calls using a shader with the given name (partial match).

Args: shader_name: Partial name to search for in shader names or entry points stage: Optional shader stage to search (if not specified, searches all stages)

Returns a list of matching draw calls with event IDs and match reasons.

Inputs: shader_name (required), stage. Returns: object

find_draws_by_textureA

Find all draw calls using a texture with the given name (partial match).

Args: texture_name: Partial name to search for in texture resource names

Returns a list of matching draw calls with event IDs and match reasons. Searches SRVs, UAVs, and render targets.

Inputs: texture_name (required). Returns: object

get_action_timingsA

Get GPU timing information for actions (draw calls, dispatches, etc.).

Args: event_ids: Optional list of specific event IDs to get timings for. If not specified, returns timings for all actions. marker_filter: Only include actions under markers containing this string (partial match). exclude_markers: Exclude actions under markers containing these strings.

Returns timing data including:

  • available: Whether GPU timing counters are supported

  • unit: Time unit (typically "seconds")

  • timings: List of {event_id, name, duration_seconds, duration_ms}

  • total_duration_ms: Sum of all durations

  • count: Number of timing entries

Note: GPU timing counters may not be available on all hardware/drivers.

Inputs: event_ids, marker_filter, exclude_markers. Returns: object

get_buffer_contentsA

Read the contents of a buffer resource.

Args: resource_id: The resource ID of the buffer to read offset: Byte offset to start reading from (default: 0) length: Number of bytes to read, 0 for entire buffer (default: 0)

Returns buffer data as base64-encoded bytes along with metadata.

Inputs: resource_id (required), length, offset. Returns: object

get_capture_statusA

Check if a capture is currently loaded in RenderDoc. Returns the capture status and API type if loaded.

Inputs: no named parameters. Returns: object

get_draw_call_detailsA

Get detailed information about a specific draw call.

Args: event_id: The event ID of the draw call to inspect

Includes vertex/index counts, resource outputs, and other metadata.

Inputs: event_id (required). Returns: object

get_draw_callsA

Get the list of all draw calls and actions in the current capture.

Args: include_children: Include child actions in the hierarchy (default: True) marker_filter: Only include actions under markers containing this string (partial match) exclude_markers: Exclude actions under markers containing these strings (list of partial matches) event_id_min: Only include actions with event_id >= this value event_id_max: Only include actions with event_id <= this value only_actions: If True, exclude marker actions (PushMarker/PopMarker/SetMarker) flags_filter: Only include actions with these flags (list of flag names, e.g. ["Drawcall", "Dispatch"])

Returns a hierarchical tree of actions including markers, draw calls, dispatches, and other GPU events.

Inputs: event_id_max, event_id_min, flags_filter, only_actions, +3 more. Returns: object

get_frame_summaryA

Get a summary of the current capture frame.

Returns statistics about the frame including:

  • API type (D3D11, D3D12, Vulkan, etc.)

  • Total action count

  • Statistics: draw calls, dispatches, clears, copies, presents, markers

  • Top-level markers with event IDs and child counts

  • Resource counts: textures, buffers

Inputs: no named parameters. Returns: object

get_pipeline_stateA

Get the full graphics pipeline state at a specific event.

Args: event_id: The event ID to get pipeline state at

Returns detailed pipeline state including:

  • Bound shaders with entry points for each stage

  • Shader resources (SRVs): textures and buffers with dimensions, format, slot, name

  • UAVs (RWTextures/RWBuffers): resource details with dimensions and format

  • Samplers: addressing modes, filter settings, LOD parameters

  • Constant buffers: slot, size, variable count

  • Render targets and depth target

  • Viewports and input assembly state

Inputs: event_id (required). Returns: object

get_shader_infoA

Get shader information for a specific stage at a given event.

Args: event_id: The event ID to inspect the shader at stage: The shader stage (vertex, hull, domain, geometry, pixel, compute)

Returns shader disassembly, constant buffer values, and resource bindings.

Inputs: stage (required), event_id (required). Returns: object

get_texture_dataA

Read the pixel data of a texture resource.

Args: resource_id: The resource ID of the texture to read mip: Mip level to retrieve (default: 0) slice: Array slice or cube face index (default: 0) For cube maps: 0=X+, 1=X-, 2=Y+, 3=Y-, 4=Z+, 5=Z- sample: MSAA sample index (default: 0) depth_slice: For 3D textures only, extract a specific depth slice (default: None = full volume) When specified, returns only the 2D slice at that depth index

Returns texture pixel data as base64-encoded bytes along with metadata including dimensions at the requested mip level and format information.

Inputs: resource_id (required), mip, slice, sample, +1 more. Returns: object

get_texture_infoC

Get metadata about a texture resource.

Args: resource_id: The resource ID of the texture

Includes dimensions, format, mip levels, and other properties.

Inputs: resource_id (required). Returns: object

list_capturesA

List all RenderDoc capture files (.rdc) in the specified directory.

Args: directory: The directory path to search for capture files

Returns a list of capture files with their metadata including:

  • filename: The capture file name

  • path: Full path to the file

  • size_bytes: File size in bytes

  • modified_time: Last modified timestamp (ISO format)

Inputs: directory (required). Returns: object

open_captureA

Open a RenderDoc capture file (.rdc).

Args: capture_path: Full path to the capture file to open

Returns success status and information about the opened capture. Note: This will close any currently open capture.

Inputs: capture_path (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 15 tools

    Disambiguation5/5

    Every tool serves a distinct purpose with clearly defined search criteria or actions. For example, find_draws_by_resource, find_draws_by_shader, and find_draws_by_texture are all differentiated by the search parameter, and get_draw_calls vs get_draw_call_details separate listing from details.

    Naming Consistency4/5

    Most tools follow the verb_noun pattern (e.g., get_draw_calls, list_captures, open_capture), but there is minor inconsistency: 'find_draws_by_resource' vs 'get_draw_calls' (different verbs), and 'get_action_timings' vs 'get_draw_call_details' (different nouns for similar concepts).

    Tool Count4/5

    15 tools is appropriate for a graphics debugger MCP server, covering capture management, draw call queries, resource inspection, pipeline state, and timing. Slightly more than minimal but well-scoped.

    Completeness4/5

    The tool set covers the main inspection workflow: open capture, list actions, get details, check pipeline state, shaders, buffers, textures, and timings. Missing features like capturing a frame or stepping through events are expected external to MCP.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      184
      -
    • A
      license
      A
      quality
      Not graded
      maintenance
      Enables 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.
      12
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI clients to analyze RenderDoc captures by browsing draw/dispatch events, inspecting pipeline state and shaders, and paginating vertex/constant buffer data.
      13
      1
      MIT