Elasticsearch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Your Elasticsearch instance URL | |
| API_KEY | No | Elasticsearch API key for authentication | |
| CA_CERT | No | Path to custom CA certificate for Elasticsearch SSL/TLS | |
| PASSWORD | No | Elasticsearch password for basic authentication | |
| 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_indicesA | List all available Elasticsearch indices, support regex |
| get_mappingsB | Get field mappings for a specific Elasticsearch index |
| searchB | Perform an Elasticsearch search with the provided query DSL. Highlights are always enabled. |
| elasticsearch_healthB | Get the health status of the Elasticsearch cluster, optionally include index-level details |
| create_indexB | Create an Elasticsearch index, optionally configure settings and mappings |
| create_mappingB | Create or update the mapping structure of an Elasticsearch index |
| bulkD | Bulk data into an Elasticsearch index |
| reindexB | Reindex data from a source index to a target index |
| create_index_templateB | Create or update an Elasticsearch index template |
| get_index_templateB | Get information about Elasticsearch index templates |
| delete_index_templateC | Delete an Elasticsearch index template |
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 11 tools
Each tool targets a distinct Elasticsearch resource and action (e.g., create_index, create_mapping, search, bulk). There is no overlap or ambiguity; tools are clearly differentiated by their purpose.
Most tools follow a verb_noun pattern with underscores (e.g., create_index, get_mappings). However, 'elasticsearch_health' deviates by starting with a noun instead of a verb, causing a minor inconsistency.
With 11 tools, the server covers a reasonable breadth of Elasticsearch operations (index management, search, mapping, templates) without being excessive. The count fits well within the typical 3-15 range for a focused server.
The tool set lacks essential operations like deleting an index and document-level CRUD (get, delete by ID). While bulk and search are present, agents cannot perform complete lifecycle management, leading to significant gaps.