Skip to main content
Glama
Ronit-k

MCPilot

by Ronit-k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCPilot

No user-submitted related servers found.

    Related Servers

    • incident-tool

      KyleCS0
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to diagnose Linux server incidents by collecting and structuring system diagnostics from multiple servers via SSH, with tools for finding incident clusters, gathering context (memory, CPU, swap, etc.), and running arbitrary commands.
      -

    • mcp-linux-tools

      gerard-kanters
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to perform controlled Linux system administration tasks like reading logs, managing services, cron jobs, WordPress, and executing sandboxed Python code, with strict security constraints.
      29
      2
      GPL 2.0

    • aiganak-aiops-mcp

      AiGanak
      A
      license
      B
      quality
      C
      maintenance
      Enables autonomous infrastructure diagnostics, log root-cause analysis, and safe code patching via tools for querying logs, inspecting Python AST, and applying git-safe patches.
      3
      Apache 2.0

    • mcp-linux-ops

      zql78
      F
      license
      B
      quality
      D
      maintenance
      Enables LLMs to execute shell commands and perform file operations on a Linux system, exposing tools like execute_command, read_file, write_file, and more.
      10
      -

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

    A4.2/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a specific resource and action: system metrics (cpu, memory, disk), process listing vs detail, service status vs logs vs restart, file operations (list, metadata, search, read), and git (status, diff, log). No two tools overlap in purpose, and descriptions clearly delineate when to use each.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: get_cpu_usage, list_processes, get_service_logs, search_files, git_status, run_tests. The git_ prefix acts as a consistent namespace, and verbs (get, list, search, read, restart, run) are unambiguous.

    Tool Count4/5

    With 18 tools, the set is slightly above the typical 3-15 sweet spot but still well-scoped for a system diagnostic server. The breadth (system, process, service, file, git, tests) justifies each tool's existence, and none feel redundant.

    Completeness3/5

    The surface covers monitoring and read-only inspection comprehensively, but notable mutating actions are missing: no process kill, no file write/edit, no git commit/push, and only restart_service (no start/stop). This limits full lifecycle management, though it may be intentional for a diagnostic tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources