Skip to main content
Glama
ntbang0901

graylog-mcp

by ntbang0901
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to graylog-mcp

No user-submitted related servers found.

    Related Servers

    • Graylog MCP Server

      jagadeesh52423
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives AI assistants direct access to your Graylog logs -- search, aggregate, analyze, and cluster log data through natural language.
      23
      19 npm
      MIT

    • loggly-mcp

      andrewbabu
      A
      license
      C
      quality
      C
      maintenance
      Read-only Model Context Protocol (MCP) server for Loggly /apiv2/* APIs, plus IP intelligence (RDAP, GreyNoise, AbuseIPDB). Exposes Loggly search/analytics/field tools, aggregation-first traffic tools, and IP-context tools
      24
      188 npm
      MIT

    • quickwit-mcp

      agarwalvivek29
      A
      license
      Not graded
      quality
      F
      maintenance
      A read-only MCP server that exposes Quickwit log search and aggregations to LLM clients, enabling natural language log investigation.
      Apache 2.0

    • seq-mcp

      MCLifeLeader
      A
      license
      D
      quality
      B
      maintenance
      A Model Context Protocol server that provides AI agents with controlled read access to Datalust Seq instances for log analysis and monitoring. It enables agents to search events, execute data queries, and retrieve information about signals, dashboards, and alerts.
      100
      3
      MIT

    • graylog-mcp

      anpy-j
      A
      license
      A
      quality
      D
      maintenance
      Provides a standardized MCP interface for querying Graylog logs, enabling AI agents to search, diagnose, and correlate runtime logs with code via configurable profiles.
      5
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 17 tools

    Disambiguation4/5

    Each tool targets a distinct query or aggregation pattern (search, count, get, histogram, top values, trace, service map). The main overlap is that root_cause conceptually aggregates error_summary, compare_periods, detect_changes and service_map, which could make an agent unsure whether to use the composite or the individual tools, but descriptions clarify root_cause as the 'start here' entry point.

    Naming Consistency4/5

    All names are snake_case with a consistent verb_noun or noun form (search_logs, count_logs, get_message, compare_periods). Some are noun phrases (error_summary, log_histogram, service_map) and others are verb-led, but the style is uniform and readable throughout.

    Tool Count4/5

    17 tools is on the heavier side but justified for a rich observability domain covering search, aggregation, tracing, topology and infrastructure discovery. No tool appears redundant or purely decorative.

    Completeness4/5

    Covers the full investigation lifecycle: search/count/get/context, time-series and top-value aggregation, error grouping, period comparison, tracing, service topology, deploy detection, and discovery of streams/fields/instances/presets. Minor gaps exist (no alert or user/config management), but they are outside the core log-investigation purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources