RenderDoc MCP Server
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中启用扩展
启动RenderDoc
工具 > 管理扩展
启用“RenderDoc MCP Bridge”
3. 安装MCP服务器
uv tool install
uv tool update-shell # PATHに追加重新启动shell后,即可使用 renderdoc-mcp 命令。
注意:添加
--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"
}
}
}使用方法
启动RenderDoc并打开捕获文件(.rdc)
从MCP客户端(如Claude)访问RenderDoc的数据
MCP工具列表
工具 | 说明 |
| 检查捕获的加载状态 |
| 以层级结构获取绘制调用列表 |
| 获取特定绘制调用的详细信息 |
| 获取着色器的源代码・常量缓冲区的值 |
| 获取缓冲区的内容(Base64) |
| 获取纹理的元数据 |
| 获取纹理的像素数据(Base64) |
| 获取管线状态 |
使用示例
获取绘制调用列表
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+
RenderDoc 1.20+
注意:仅在Windows + DirectX 11环境下进行了操作确认。 在Linux/macOS + Vulkan/OpenGL环境下也可能运行,但尚未验证。
许可证
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables 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.150
- AlicenseAqualityNot gradedmaintenanceEnables 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
- AlicenseNot gradedqualityDmaintenanceExposes RenderDoc capture analysis to AI clients via MCP, enabling offline analysis of .rdc files (action tree, pipeline state, textures, shaders) and GUI state interaction on Windows.2MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to access RenderDoc capture data and assist in graphics debugging via a file-based IPC bridge.15482MIT
Related MCP Connectors
Live browser debugging for AI assistants — DOM, console, network via MCP.
Search your AI chat history (ChatGPT, Claude, Codex) from any MCP client. Remote, private, read-only
Provides AI assistants with direct access to Mapbox developer APIs and documentation.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ZylNice/RenderdocMCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server