SEQ MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_eventsC | Search for events in SEQ logs with powerful filtering |
| get_eventC | Get detailed information about a specific log event |
| analyze_logsC | Analyze log patterns and statistics over a time period |
| list_signalsB | List all configured signals (saved searches) in SEQ |
| check_healthB | Check the health status of the SEQ server |
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 5 tools
Each tool has a clearly distinct purpose: analyze_logs for pattern analysis, check_health for server status, get_event for retrieving specific events, list_signals for listing saved searches, and search_events for filtered searches. There is no overlap in functionality, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern with clear, descriptive verbs (analyze, check, get, list, search) and specific nouns (logs, health, event, signals, events). The naming is uniform and predictable throughout the set.
With 5 tools, the server is well-scoped for log management and monitoring in SEQ. Each tool serves a distinct and necessary function, such as health checks, event retrieval, and log analysis, without being overly sparse or bloated.
The toolset covers core log management operations well, including health monitoring, event retrieval, searching, and analysis. A minor gap exists in update/delete operations for signals or events, but agents can likely work around this for typical monitoring workflows.