Skip to main content
Glama
jperelli

Graylog MCP Server

by jperelli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Graylog MCP Server

No user-submitted related servers found.

    Related Servers

    • Overwatch MCP

      malindarathnayake
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables querying logs and metrics from Graylog, Prometheus, and InfluxDB 2.x. It provides tools for executing Lucene log searches, PromQL queries, and Flux queries directly within MCP-compatible clients.
      MIT

    • 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
      13 npm
      MIT

    • elastic-mcp

      jrvalinas
      A
      license
      B
      quality
      D
      maintenance
      Small production-oriented MCP server for diagnosing incidents from Elasticsearch logs with unknown schema. It provides tools for log discovery, retrieval, and issue diagnosis.
      6
      MIT

    • log-mcp

      ascii766164696D
      A
      license
      A
      quality
      D
      maintenance
      MCP server for log file analysis. Gives LLMs the ability to efficiently analyze large log files without loading them into context.
      7
      100
      MIT

    • elasticsearch-logs

      ws135y
      F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for Elasticsearch log querying. Enables natural language search, filtering, context retrieval, and aggregation of logs.
      -

    • graylog-mcp

      anpy-j
      A
      license
      A
      quality
      C
      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
    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.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search returns raw log lines, analyze aggregates them, get_message fetches a full document, list_streams enumerates available streams, and list_fields enumerates available fields. Even though analyze and search both query messages, their descriptions make the difference unmistakable: one for counting/aggregating, one for reading individual lines.

    Naming Consistency4/5

    All tool names use lowercase snake_case and begin with an imperative verb, which is predictable. The pattern is slightly mixed between bare verbs (search, analyze) and verb_noun compounds (list_streams, list_fields, get_message), but this is a minor deviation rather than a chaotic mix.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose: querying logs, aggregating them, inspecting single messages, and discovering streams/fields. Each tool earns its place and there is no redundancy or bloat.

    Completeness5/5

    The tool surface covers the full read-only log analysis workflow: discover available fields and streams, search for raw messages, aggregate to find patterns, and drill into a specific message. There are no obvious dead ends, and the descriptions explicitly guide the agent on how to combine tools for effective use.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources