MCP Graylog Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | INFO |
| LOG_FORMAT | No | Log format (json/text) | json |
| GRAYLOG_TIMEOUT | No | Request timeout (seconds) | 30 |
| MCP_SERVER_HOST | No | MCP server host | 0.0.0.0 |
| MCP_SERVER_PORT | No | MCP server port | 8000 |
| GRAYLOG_ENDPOINT | Yes | Graylog server URL | |
| GRAYLOG_PASSWORD | Yes | Graylog password | |
| GRAYLOG_USERNAME | Yes | Graylog username | |
| GRAYLOG_VERIFY_SSL | No | Verify SSL certificates | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_logsD | – |
| search_stream_logsD | – |
| aggregate_logsD | – |
| list_streamsD | – |
| get_stream_infoD | – |
| search_streams_by_nameD | – |
| get_system_infoD | – |
| get_error_logsD | – |
| get_log_count_by_levelD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Some tools have overlapping functionality, such as search_logs and search_stream_logs, or aggregate_logs and get_log_count_by_level, which could cause confusion. However, most tools target distinct resources or actions.
Tools follow a snake_case pattern with verbs like get, list, search, aggregate. The pattern is mostly consistent but not perfectly uniform, e.g., list_streams vs get_stream_info.
9 tools is appropriate for a Graylog server, covering the main read operations without being excessive. It feels well-scoped.
The set covers common query and retrieval operations but lacks write or management tools (e.g., create stream, update). It seems focused on read-only access, which may be intentional but is incomplete for full lifecycle.