Skip to main content
Glama
parajiholkar

Multi-Container Log Correlator MCP Server

by parajiholkar

Related Servers

Alternatives to Multi-Container Log Correlator MCP Server

No user-submitted related servers found.

    Related Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides comprehensive logging and monitoring capabilities for MCP services with real-time log tailing, advanced search, error analysis, and anomaly detection. Enables centralized log aggregation, correlation tracking, and health monitoring across all MCP ecosystem services.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables querying and searching logs from Kibana (ELK stack) via MCP, with support for project-based data views, trace ID correlation, and log expansion.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables log analysis through MCP tools for searching logs, retrieving error contexts, and summarizing incidents with self-verified root-cause hypotheses.
      4 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible coding agents to debug applications using runtime log data, by providing tools to start a local log-ingestion server, track debugging sessions and hypotheses, and correlate logs to specific executions.
      19
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes configured log files as MCP tools, enabling agents to list, query, and follow logs from local and SSH sources.
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      A log analysis MCP server that enables tailing, searching, filtering, and summarizing logs from local files and Docker containers.
      7
      -

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with the main overlap being tail_service_errors and tail_service_logs when level_filter includes ERROR/FATAL. The descriptions mitigate this by positioning tail_service_errors as the fast error-spotting tool, but an agent could still reasonably confuse which to call.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb-first pattern: list, search, get, tail. The naming style is predictable and makes it easy to infer what each tool does before reading its description.

    Tool Count5/5

    Seven tools is a well-scoped count for a log correlation server. Each tool covers a distinct aspect of the debugging workflow without feeling bloated or too sparse.

    Completeness4/5

    The set covers container discovery, stats, error tailing, general log tailing, full-text search, trace ID listing, and trace-correlated timelines. A notable minor gap is the lack of explicit time-range based log queries, but the core distributed debugging workflow is well supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues