Elasticsearch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ES_URL | No | Your Elasticsearch instance URL | |
| ES_API_KEY | No | Elasticsearch API key for authentication | |
| ES_CA_CERT | No | Path to custom CA certificate for Elasticsearch SSL/TLS | |
| ES_PASSWORD | No | Elasticsearch password for basic authentication | |
| ES_USERNAME | No | Elasticsearch username for basic authentication |
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 |
|---|---|
| list_indicesC | List all available Elasticsearch indices |
| get_mappingsB | Get field mappings for a specific Elasticsearch index |
| searchB | Perform an Elasticsearch search with the provided query DSL. Highlights are always enabled. |
| get_shardsC | Get shard information for all or specific indices |
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 4 tools
Each tool has a clearly distinct purpose targeting different aspects of Elasticsearch operations: get_mappings for field structure, get_shards for infrastructure details, list_indices for inventory, and search for querying data. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern (get_mappings, get_shards, list_indices, search) with clear, descriptive verbs. The naming is uniform and predictable throughout the set.
With only 4 tools, the set feels thin for an Elasticsearch server, lacking essential operations like create/update/delete indices or documents. While the tools are well-scoped, the count is borderline low for the domain's typical scope.
The tool surface has significant gaps for an Elasticsearch domain: it includes read-only operations (get, list, search) but completely misses write operations (e.g., index, update, delete), configuration management, or cluster operations. This will likely cause agent failures in common workflows.