Skip to main content
Glama
link0-o

PerfLens MCP Server

by link0-o
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to PerfLens MCP Server

No user-submitted related servers found.

    Related Servers

    • xcodeinstrumentmcp

      eksdev007
      A
      license
      Not graded
      quality
      D
      maintenance
      Local-first CLI and MCP server for turning Xcode Instruments artifacts into bounded, agent-sized evidence, with support for analyses like Time Profiler, Allocations, Network, and more.
      2
      MIT

    • linux-profiler

      yuezhongtao
      A
      license
      A
      quality
      C
      maintenance
      A comprehensive Linux system performance profiler with MCP remote invocation support, featuring advanced process profiling and flame graph generation.
      10
      2
      Apache 2.0

    • perf-mcp

      walac
      F
      license
      A
      quality
      C
      maintenance
      Enables LLMs to analyze Linux perf data files using 26 perf analysis commands, including report, script, annotate, and more, through typed tool parameters.
      26
      -

    • SysMCP

      thealonemusk
      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.
      -

    • flameox

      morluto
      A
      license
      C
      quality
      A
      maintenance
      Enables coding agents to query, compare, and audit local profiler traces, benchmarks, memory captures, and execution evidence without uploading code or data, using CLI and MCP interfaces.
      111
      121
      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.1/5.0

    Scored across 38 tools

    Disambiguation2/5

    Several tool families have dangerously similar names and overlapping purposes, especially the three authorize_docker_*_session tools, the three collect_docker_* tools, and the inspect_*_capability/capabilities tools. Though the descriptions are explicit and clarify boundaries, an agent would need to read long, nuanced descriptions carefully to avoid misselecting the wrong authorization or collection mode.

    Naming Consistency4/5

    Tool names overwhelmingly follow a clear verb_noun snake_case pattern, and there is no mixing of camelCase or wildly different conventions. Minor inconsistencies exist in modifier placement (managed_docker vs docker_optimization) and singular/plural mismatches like capabilities vs capability, but the overall naming style is predictable.

    Tool Count2/5

    38 tools is well above the 25+ threshold that indicates an overgrown surface. The workflows are complex, but the count is unwieldy and many tools are fine-grained variations of the same operation family, making the set feel heavier than its core purpose requires.

    Completeness4/5

    The tool set covers the apparent performance-analysis and Docker-optimization domain broadly: inspection, authorization, collection, analysis, verification, comparison, source resolution, diagnosis, and cleanup. Minor gaps like generic artifact deletion or session-status listing exist, but agents can work around them via read_artifact_page and the existing lifecycle tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources