Graphics Capture Automation#
Use the automation interfaces included in your Nsight Graphics package to investigate an existing capture. The Model Context Protocol (MCP) server also provides workflows for acquiring new captures and profiling data. These preview interfaces may change between releases. Keep the original capture and record the Nsight Graphics version when sharing an analysis.
MCP Preview#
MCP connects a compatible agent application to Nsight Graphics tools. The following setup covers the Windows desktop x64 package. Run the agent and the server on the same Windows machine, with access to the capture files and any application you intend to analyze.
Start ngfx-mcp.exe from the installed host/windows-desktop-nomad-x64 directory:
& 'C:\path\to\Nsight Graphics\host\windows-desktop-nomad-x64\ngfx-mcp.exe'
In the agent application’s MCP settings, add a Streamable HTTP server with the URL
http://127.0.0.1:7661/mcp. Leave the server running while the agent is connected. This default
Workflow profile offers a compact workflow for acquiring and inspecting graphics data. Ask
the agent to inspect the API manifest before choosing tools, and give it the absolute path to an
existing capture and a specific question, for example:
Inspect C:\captures\frame.ngfx-capture. List the draw calls in the first frame
and identify their bound shaders. Start with offline inspection.
For more detailed experimental tools, configure an MCP client to launch ngfx-mcp.exe with
--profile native --transport stdio. The Native catalog uses progressive tool discovery;
its tool names and session behavior differ from Workflow. Match the client configuration to the
selected profile rather than switching transports alone.
Keep the installed host and target files together. Available tools depend on the package and the underlying activity support. Live operations also require the GPU, driver, and application prerequisites of the corresponding Nsight Graphics activity. Review the evidence returned by the agent before acting on its conclusions.