Skip to main content
Glama
scarletfantasy

nsight-graphics-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NSIGHT_GRAPHICS_CLINoFull path to ngfx.exe used for GPU Trace. Discovered from the replayer installation directory if not specified.
NSIGHT_MCP_CACHE_MBNoLRU memory cache limit for parsed and desensitized data.256
NSIGHT_GRAPHICS_REPLAYERNoFull path to ngfx-replay.exe. By default, the server auto-selects the version from the standard installation directory.
NSIGHT_MCP_MAX_EXPORT_MBNoSafety cap for a single Nsight JSON export.512
NSIGHT_MCP_MAX_GPUTRACE_MBNoFile read cap for .ngfx-gputrace.1024
NSIGHT_GRAPHICS_INSTALL_DIRNoNsight Graphics installation root directory. Auto-discovered if not specified.
NSIGHT_GRAPHICS_WARPVIZ_PLUGINNoPath to WarpViz plugin that matches the report version, used to read embedded protobuf schemas. Discovered from the replayer installation directory if not specified.
NSIGHT_MCP_MAX_REPORT_SESSIONSNoMaximum number of GPU Trace report sessions allowed in the same MCP process.4
NSIGHT_MCP_MAX_CONCURRENT_REPLAYSNoNumber of simultaneous GPU Trace/profile replays; default is 1 to serialize and avoid GPU contention and data pollution.1
NSIGHT_MCP_MAX_GPUTRACE_METADATA_MBNoDecompressed WRPV protobuf metadata cap.512

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
nsight_statusA

Locate the local NVIDIA Nsight Graphics ngfx-replay executable and report its version and MCP cache status.

inspect_captureA

Read capture identity, application/GPU/API/version metadata, portability flags, and replay incompatibilities without replaying the frame. Environment values are never returned.

analyze_captureA

Build a bounded static analysis from Nsight metadata, API event names, and object identities: stream shape, top calls, thread distribution, resource population, compatibility/security findings, and explicit limitations.

list_capture_eventsA

Page through the exported API function stream. Filter by function-name regex, inferred category, thread, or event-index range. Results contain names and indices, not call parameters or timings.

list_capture_resourcesA

Page through captured object identities and filter by UID, API, type, object-name substring, creator-function substring, or nonzero access flags.

get_capture_logsA

Read captured Nsight/application log messages with optional error-only mode, text search, and pagination. Credential-shaped values are redacted.

extract_capture_screenshotA

Extract the final-present screenshot embedded in a capture. Without output_path it returns an MCP image using a temporary file. With output_path it also saves the image; existing files require overwrite=true.

get_gpu_trace_summaryA

Run Nsight GPU Trace on one hidden replay pass and return the Summary-tab range, Top-Level Throughput, Active Threads Per Warp, and SM Warp Occupancy data. This executes instrumented GPU work and can take several minutes for large captures.

collect_gpu_trace_reportA

Run a feature-rich Nsight GPU Trace replay, retain its report and auto-export tables in a report session, and return a report_id. Query that id with the metric, range, trace-information, and shader-occupancy tools. Collection executes instrumented GPU work and can take several minutes.

open_gpu_trace_exportA

Open an existing Nsight GPU Trace auto-export directory and register it as a queryable report session without replaying the capture. The directory must contain FRAME.xls and GPUTRACE_FRAME.xls, directly or in a child auto-export folder.

list_gpu_trace_reportsA

List queryable GPU Trace reports currently registered in this MCP process.

list_gpu_trace_metricsA

Page through every exported GPU Trace metric for the full frame or a marker range. Metrics preserve their raw Nsight names and numeric values and add inferred display groups and units.

list_gpu_trace_rangesB

Page through exported marker/regime ranges with hierarchy, path, parent id, and measured duration. A returned range_id can be used by the metric, summary, and shader-occupancy tools.

summarize_gpu_trace_rangeA

Return the same Top-Level Throughput, Active Threads Per Warp, and SM Warp Occupancy summary for the full trace or one exported marker range.

get_gpu_trace_informationA

Read the exported Trace Information name/value table, including collection and replay configuration. Credential-shaped values are redacted.

list_gpu_trace_shader_occupancyA

Page through per-shader PC-sampler occupancy rows for the full trace or one marker range. Returns the exact exported shader name/hash and aggregate warps/occupancy; stage is explicitly heuristic.

get_gpu_trace_report_overviewA

Inspect the retained .ngfx-gputrace WRPV container and return frame timing, queues, command-stream/API-call counts, timestamp coverage, shader-profiler inventory, and the version-matched embedded protobuf schema inventory.

list_gpu_trace_timeline_eventsA

Page through queue command-stream calls decoded from .ngfx-gputrace, including queue identity and timestamp intervals. Coalesced intervals explicitly identify calls that share one measured timing group.

get_gpu_trace_timeline_eventA

Return one decoded GPU Trace command-stream call with full typed arguments, return value, object handles, timestamp boundaries, pipeline stages, and HES correlation ids. Embedded byte arrays are represented by byte length, not dumped.

list_gpu_trace_marker_rangesA

Page through D3D12 BeginEvent/EndEvent ranges decoded from the binary report, including full marker path, hierarchy, absolute frame-relative start/end time, timing uncertainty bounds, and the paired timeline event ids. These marker ids can directly scope PC-sampling analysis.

list_gpu_trace_shader_pipelinesA

Page through Shader Pipelines data decoded from the binary report and joined with raw PC samples and exported metrics: pipeline type/name, shader stage/hash, exact sample count/share, DXIL or SPIR-V correlation, code address/size, registers, group size, barriers, shared memory, and debug-info availability. An explicitly named estimate is also returned as fallback/comparison.

list_gpu_trace_shader_objectsA

Return the Shader Pipelines table grouped by Shader Object: exact shader stage/name/hash, raw PC-sample count and Samples %, DXIL/SPIR-V correlation, debug-blob reference state, and referencing pipelines. A blob reference does not imply complete source/call-stack debug information. Sample counts cover Entire Trace.

analyze_gpu_trace_pc_samplingA

Decode raw PC-sampling records into sample/stall reasons, exact shader/code-block attribution, and top shader and instruction-PC hotspots. Scope the query to the entire trace, a frame-relative time window, or a timed marker id such as BasePass. This does not require shader PDBs; source-line and SASS text correlation are not claimed.

release_gpu_trace_reportA

Unregister a GPU Trace report. Temporary artifacts created without output_directory are deleted; user-selected persistent output directories are never deleted.

profile_captureA

Replay the capture in a hidden, vsync-off window and summarize Nsight's per-iteration CPU submit, finish-wait, reset, FPS, screenshot-difference, and optional GPU frame-time measurements. This executes GPU work; it is not a static read.

clear_capture_cacheA

Clear in-memory sanitized Nsight export data held by this MCP process.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

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/scarletfantasy/nsight-graphics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server