Skip to main content
Glama
yufeizhou666

log-analyzer-mcp

by yufeizhou666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to log-analyzer-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-system-monitor

      VZilvinskus
      F
      license
      A
      quality
      D
      maintenance
      Enables Claude to monitor CPU, memory, disk, processes, network connections, Docker containers, and system logs for system diagnostics and troubleshooting.
      5
      -

    • mcp-it-ops

      bastiaan365
      F
      license
      A
      quality
      D
      maintenance
      Exposes homelab and IT-ops tools to Claude, including system health monitoring, Grafana alert states, Docker container status, Loki logs, SMART disk health, and more.
      8
      1
      -

    • ai-ssh-mcp

      guozhiwei01
      A
      license
      A
      quality
      D
      maintenance
      Enables natural language SSH server management via Claude Code, allowing users to read logs, check services, run commands, and transfer files across multiple servers.
      6
      MIT

    • 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

    • datadog-aws-mcp

      edxmorales
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that exposes tools to query Datadog monitors and logs, and AWS CloudWatch Logs, and to group recurring errors by fingerprint. Designed for use with Claude Code to diagnose issues and propose fixes.
      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 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: counting by level, error explanation, system metrics, time-range queries, and keyword search. No overlap in functionality.

    Naming Consistency4/5

    Names follow a verb-oriented pattern (count, explain, get, query, search) but mix styles: some use 'by_' (count_by_level, query_by_timerange) while others are plain verb_noun (explain_error, get_system_metrics, search_logs). Mostly consistent but with minor deviations.

    Tool Count5/5

    5 tools is well-scoped for a log analysis server, covering essential operations without being too few or excessive.

    Completeness4/5

    Core log analysis tasks are covered: search, count by level, time-range queries, error explanation, and system metrics. Minor gaps exist, such as lacking a tool to list log sources or aggregate statistics beyond level counting.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources