Skip to main content
Glama
scarletfantasy

pix-mcp

by scarletfantasy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to pix-mcp

No user-submitted related servers found.

    Related Servers

    • nsight-graphics-mcp

      scarletfantasy
      A
      license
      A
      quality
      C
      maintenance
      MCP server for reading, filtering, and analyzing NVIDIA Nsight Graphics captures via ngfx-replay, exposing tools for capture inspection, GPU Trace profiling, and replay analysis.
      26
      MIT

    • pix-mcp

      elliotttate
      A
      license
      Not graded
      quality
      D
      maintenance
      Wraps Microsoft PIX's pixtool.exe to enable LLMs to launch and attach to D3D12 processes, capture GPU traces, and perform fine-grained queries (e.g., root parameter bindings at specific events) without manual CSV dumps.
      2
      MIT

    • RenderDoc MCP

      LifeSugar
      A
      license
      B
      quality
      C
      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
      MIT

    • RenderDoc MCP Server

      ZylNice
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to access RenderDoc capture data and assist with graphics debugging by retrieving draw calls, shader information, buffers, textures, and pipeline state.
      15
      MIT

    • dcc-mcp-renderdoc

      dcc-mcp
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables automated graphics capture and replay with RenderDoc, allowing agents to launch executables, inspect captures, and export thumbnails or timeline JSON for regression triage.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 67 tools

    Disambiguation3/5

    Most tools have distinct purposes, but a few pairs overlap, such as pix_list_queues vs pix_discover_queues and pix_list_events vs pix_list_gpu_events. The detailed descriptions help, but the large number of tools makes misselection more likely.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern with the pix_ prefix, such as list_resources, get_pipeline_state, and capture_timing. This consistency makes the tool's action and target predictable across the entire set.

    Tool Count2/5

    With 67 tools, this far exceeds the typical well-scoped MCP server range. While the PIX domain is broad, the count is unwieldy and could benefit from being split into focused servers by area such as capture, timing, or GPU analysis.

    Completeness5/5

    The tool set covers the full capture-analysis lifecycle: capture from various targets, open/close/upgrade captures, inspect GPU/CPU timing, events, resources, pipeline state, counters, occupancy, memory, input, and export. No obvious dead ends or missing core operations are apparent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources