Skip to main content
Glama
Sign In
Log Detective MCP

Log Detective MCP

Official
by fedora-copr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Log Detective MCP

No user-submitted related servers found.

    Related Servers

    • log-ai-compressor

      hu-chenyu
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to analyze, cluster, compare, and export reports from local log files through seven read-only tools, returning compact evidence packs with line-number citations instead of raw log dumps. All processing happens on the local machine, so log data never leaves the environment.
      63 PyPI
      1
      MIT

    • log-essence

      Apsion
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables LLMs to analyze logs by extracting patterns, redacting secrets, and providing token-efficient summaries from files, Docker containers, or journald.
      5
      MIT

    • logs-mcp

      0xmortuex
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to investigate very large log files with constant-memory streaming, offering format overviews, filtered searches, error clustering, timelines, request tracing, and window comparisons across plain, gzipped, and rotated logs.
      MIT

    • log-ai-optimizer

      JustinHabashi
      F
      license
      Not graded
      quality
      D
      maintenance
      Compresses log files into templates and statistics using Drain3, and exposes them to AI assistants via an MCP server for efficient log monitoring and anomaly detection.
      -

    • Drain3 MCP Server

      xinqihuang
      A
      license
      A
      quality
      D
      maintenance
      MCP server that wraps Drain3 for streaming log template mining, read-only matching, parameter extraction, and model persistence, exposing tools and resources to train on logs and query learned templates.
      8
      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

    A3.9/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools target different extraction strategies (Drain3 clustering vs Python traceback heuristics), so their core purposes are clearly distinct. However, they share identical input modes (log_text/log_path/log_url, skip_patterns, context), and a log containing tracebacks could plausibly be fed to either, leaving a small boundary ambiguity an agent must reason about.

    Naming Consistency5/5

    Both names follow the same `extract_<thing>` snake_case convention with the same verb prefix and noun-phrase object. Parameter naming is also mirrored across the two tools (max_*_len, skip_patterns, context), reinforcing predictability.

    Tool Count3/5

    Two tools is thin for a server branded as 'Log Detective' — the surface is essentially one extraction family with two strategies. It is not incoherent, but there is little room for an agent to do anything beyond pulling snippets or tracebacks.

    Completeness3/5

    Input handling is thorough (text/path/URL, transparent decompression, safety limits) and both tools mirror it consistently. But the lifecycle stops at extraction: there is no summarization, severity/error-level grouping, keyword or pattern-include extraction, or structured output option, which leaves gaps for a diagnostic-oriented server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources