graylog-mcp
Related Servers
Alternatives to graylog-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that gives AI assistants direct access to your Graylog logs -- search, aggregate, analyze, and cluster log data through natural language.2373 npmMIT
- AlicenseCqualityCmaintenanceRead-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 tools2443 npmMIT
- AlicenseNot gradedqualityFmaintenanceA read-only MCP server that exposes Quickwit log search and aggregations to LLM clients, enabling natural language log investigation.Apache 2.0
- AlicenseBqualityCmaintenanceA portable, read-only Model Context Protocol server for turning observability data into bounded evidence that AI agents can inspect safely.7Apache 2.0
- AlicenseDqualityCmaintenanceA 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.1003MIT
- AlicenseAqualityDmaintenanceProvides a standardized MCP interface for querying Graylog logs, enabling AI agents to search, diagnose, and correlate runtime logs with code via configurable profiles.5MIT
TDQS
Scored across 9 tools
Each tool has a reasonably distinct role, and the descriptions include explicit routing hints ('start here for is anything wrong' vs 'what is causing this incident') that separate scan from root_cause. The main soft overlaps are search_logs vs run_preset and aggregate kind='errors' vs scan/compare_periods, but those are clarified enough in text to avoid most misselection.
All names use snake_case and most are verb-first (search_logs, get_message, trace_request, compare_periods, run_preset). Minor deviations are single-verb names (describe, aggregate, scan) and a noun name (root_cause), so the pattern is predictable but not perfectly uniform.
Nine tools is well within the ideal 3-15 range and every tool corresponds to a distinct investigative need (discover, search, count, inspect, trace, compare, scan, diagnose, replay preset). No tool looks like filler and none is obviously missing at this scale.
The surface covers the full read-only log-analysis lifecycle: metadata discovery, querying, aggregation, single-message inspection, cross-service tracing, period comparison, health scanning, root-cause verdicts, and saved presets. Gaps are minor, e.g. no explicit handling of alerts/events or saved-search management, but no typical agent workflow dead-ends.