Skip to main content
Glama

Related Servers

Alternatives to metal-gpu-trace

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables GPU profiling and performance analysis via NVIDIA Nsight Systems, allowing agents to profile binaries and aggregate statistics for kernels, memory copies, and NVTX ranges. It supports advanced analysis through interval tree construction and structural queries on profiling reports.
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to profile and disassemble GPU kernels, benchmark and compare candidate rewrites against baselines, and run an autonomous speedrun loop that verifies and records results.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to profile iOS/macOS apps using Xcode Instruments, automate simulator interactions, and get structured performance data for optimization.
      37
      16 npm
      19
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to turn explicit artifacts or commands into bounded local runtime evidence from profilers, benchmarks, trace processors, and direct targets, with typed provenance, coverage, and optional durable preservation. It exposes analysis and capture tools for tracing, profiling, and investigating hotspots in application and native code, GPU kernels, and inference stacks.
      -
    • F
      license
      A
      quality
      D
      maintenance
      Enables natural language profiling of iOS apps using xctrace (Instruments) for performance analysis like launch time, memory leaks, CPU usage, and network requests.
      12
      -

    TDQS

    A3.6/5.0

    Scored across 8 tools

    Disambiguation4/5

    Tools cluster into three clear groups (perf_* recordings, trace_* .trace exploration, capture_* .gputrace exploration) plus a standalone reference tool, and within each group the actions are distinct. The only mild risk is confusing trace_* and capture_* since both inspect capture files, but the descriptions clearly separate .trace from .gputrace.

    Naming Consistency4/5

    All names use consistent snake_case with a group prefix (perf_, trace_, capture_) that maps predictably to the domain area. Minor deviations: perf_runs and trace_tables use nouns rather than the verb style of their siblings, but the pattern remains readable.

    Tool Count5/5

    Eight tools is well-scoped for a Metal tracing/analysis server, with each tool earning its place across recording, comparison, trace exploration, capture inspection, and reference lookups.

    Completeness4/5

    The surface covers the full workflow: record, list, compare, inspect trace tables/rows, and read gputrace captures, plus a GPU-family reference. Minor gaps like no delete/prune of saved recordings or export of results exist, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues