{"id":"linkingooo-renderdoc-mcp","name":"renderdoc-mcp","af_score":66.8,"security_score":20.5,"reliability_score":26.2,"what_it_does":"renderdoc-mcp is an MCP (Model Context Protocol) server that uses RenderDoc’s headless Python replay API to analyze GPU frame capture files (.rdc). It exposes many MCP tools for session/capture management, event navigation, pipeline/shader inspection, resource export/extraction, pixel diagnostics, and performance/pass analysis.","best_when":"You have local RenderDoc installed, can point the MCP server to the RenderDoc module, and want an AI agent to drive systematic, reproducible analysis of captured frames in a headless workflow.","avoid_when":"You need a hosted API with robust authentication, rate limiting, and operational guarantees; this project appears to be a local developer tool rather than a managed service.","last_evaluated":"2026-03-30T15:23:38.598176+00:00","has_mcp":true,"has_api":false,"auth_methods":["No authentication mechanism documented; intended for local MCP client/server usage"],"has_free_tier":false,"known_gotchas":["Requires RenderDoc Python module (renderdoc.pyd/renderdoc.so) and correct RENDERDOC_MODULE_PATH; tool execution may fail if the module path is wrong.","Some event/pipeline queries likely require navigation via set_event before calling pipeline/detail tools (README notes set_event is required before pipeline queries).","Large exports (batch texture export, pixel history) may be slow/heavy; no rate limiting or workload guidance documented.","Captures are stateful per session (open_capture auto-closes previous capture); agents should manage session lifecycle carefully (open->analyze->close)."],"error_quality":0.0}