Skip to main content
Glama
walac

perf-mcp

by walac

Related Servers

Alternatives to perf-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Helps AI assistants optimize Linux workloads on Arm64 by parsing perf report output, recommending NEON SIMD intrinsics for hot loops, and auditing Python dependency manifests for arm64 wheel availability — all offline and structured.
      4
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to safely write and run bpftrace scripts against the Linux kernel for observability, with explicit probe allowlists and execution timeout.
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to perform high-performance code search and analysis across multiple languages using symbol indexing, regex text search, and structural AST pattern matching. It also provides tools for technology stack detection and dependency analysis with persistent caching for optimized performance.
      8
      -
    • A
      license
      B
      quality
      A
      maintenance
      Provides typed, paginated tools for evidence-driven Linux performance analysis including profile analysis, comparison, and report generation with server-side authorization.
      38
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to autonomously diagnose Linux performance issues by exposing production-debugging primitives such as perf, strace, /proc, flamegraphs, and eBPF as safe, structured, budgeted tools.
      -

    TDQS

    A3.8/5.0

    Scored across 26 tools

    Disambiguation5/5

    Each tool wraps a distinct perf subcommand with a unique analysis purpose, from report and annotate to sched-specific and kwork-specific views. Even similar tools like perf_sched_latency vs perf_sched_timehist are clearly differentiated by their descriptions.

    Naming Consistency5/5

    All tools follow the exact perf_<subcommand> pattern, with no mixing of casing or verb styles. The naming is uniform and predictable, making the toolset easy to navigate.

    Tool Count2/5

    At 26 tools, the server exceeds the 25-tool threshold for 'too many'. While perf is a broad domain, this many tools risks overwhelming an agent, and several are niche or could be consolidated.

    Completeness2/5

    The toolset is heavily analysis-focused but completely lacks capture tools like perf_record or perf_stat, making it impossible to generate the very perf.data files most tools require. This is a significant gap that forces the agent to depend on external data sources.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues