graylog-mcp
Related Servers
Alternatives to graylog-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to query and analyze Graylog logs through MCP tools for search, aggregation, stream listing, and saved queries, with optional OpenAI-powered natural language orchestration and audit logging.-
- AlicenseAqualityDmaintenanceAn MCP server that gives AI assistants direct access to your Graylog logs -- search, aggregate, analyze, and cluster log data through natural language.2316 npmMIT
- FlicenseBqualityCmaintenanceEnables AI-assisted analysis of log files through advanced searching, filtering, and test execution capabilities. Supports time-based queries, pattern matching, test summarization, and code coverage reporting directly within compatible MCP clients.12-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query and analyze logs from Graylog instances using universal search with relative or absolute time windows, supporting both full result retrieval and lightweight count-only queries.10 npm1MIT
- AlicenseAqualityCmaintenanceEnables LLM agents to search and analyze Elasticsearch logs for errors, detect recurring patterns, analyze error-rate trends, and retrieve full trace context through MCP tools.6MIT
- AlicenseAqualityCmaintenanceEnables querying Graylog log management system for messages using natural language, supporting multiple instances and flexible search parameters.124 npm10MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing profiles, fetching a specific profile, checking system info, searching messages, and running log diagnosis. Even the two profile tools are differentiated by list vs. single get, matching standard patterns.
All tools follow the consistent verb_noun pattern with a common 'graylog_' prefix: list_profiles, get_profile, get_system_info, search_messages, diagnose_code_logs. The verbs are clear and uniform in style.
Five tools is well within the ideal range for a focused MCP server. Each tool is purposeful and contributes to the overall workflow of profile-based log diagnosis without redundancy.
The tool surface covers the core workflow: retrieving diagnosis profiles, searching raw messages, and running a specialized diagnosis. Minor gaps exist, such as no tool for creating/updating profiles or fetching a single message by ID, but these are not critical for the stated purpose.