elastic-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Check Elasticsearch connectivity and return cluster basics. |
| discover_log_schemaA | Discover likely timestamp/message/service/level/correlation fields. |
| get_latest_logsB | Fetch latest logs, optionally filtered by service and level. Use exclude_messages to filter out logs matching wildcard patterns (e.g. ["/health", "heartbeat"]). |
| get_logs_for_serviceB | Fetch logs for a service in a chosen time range. Use exclude_messages to filter out logs matching wildcard patterns (e.g. ["/health", "heartbeat"]). |
| get_logs_by_correlation_idC | Fetch all logs for a correlation/trace/request id. Use exclude_messages to filter out logs matching wildcard patterns (e.g. ["/health", "heartbeat"]). |
| diagnose_issueC | Convenience diagnosis tool combining search + small summary. Use exclude_messages to filter out logs matching wildcard patterns (e.g. ["/health", "heartbeat"]). |
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 6 tools
Tools are mostly distinct, but get_latest_logs and get_logs_for_service overlap in purpose, differing mainly by time range. diagnose_issue also combines existing functionality but is clearly a convenience wrapper.
All tool names follow a consistent verb_noun pattern: check_, discover_, get_, diagnose_. No mixed conventions or vague verbs.
6 tools is well-scoped for an Elasticsearch log diagnosis server, covering connectivity, schema discovery, log retrieval, and diagnosis without unnecessary bloat.
The toolset covers the full log diagnosis workflow: checking connectivity, discovering schema, fetching logs by time/service/correlation, and a combined diagnosis tool. No obvious missing capabilities for the stated purpose.