octodet-elasticsearch-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
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 with detailed information |
| get_mappingsB | Get field mappings for a specific Elasticsearch index |
| searchC | Perform an Elasticsearch search with the provided query DSL, highlighting, and script fields |
| get_cluster_healthB | Get health information about the Elasticsearch cluster |
| get_shardsC | Get shard information for all or specific indices |
| add_documentC | Add a new document to a specific Elasticsearch index |
| update_documentC | Update an existing document in a specific Elasticsearch index |
| delete_documentB | Delete a document from a specific Elasticsearch index |
| update_by_queryC | Update documents in an Elasticsearch index based on a query |
| delete_by_queryB | Delete documents in an Elasticsearch index based on a query |
| bulkC | Perform multiple document operations (create, update, delete) in a single API call |
| create_indexB | Create a new Elasticsearch index with optional settings and mappings |
| delete_indexC | Delete an Elasticsearch index |
| count_documentsB | Count documents in an index, optionally filtered by a query |
| get_templatesC | Get index templates from Elasticsearch |
| get_aliasesC | Get index aliases from Elasticsearch |
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 16 tools
Every tool has a clearly distinct purpose targeting specific Elasticsearch operations with no ambiguity. For example, 'add_document' vs 'update_document' vs 'delete_document' are clearly differentiated, and cluster operations like 'get_cluster_health' are separate from index operations like 'list_indices'.
All tools follow a consistent verb_noun pattern throughout, using snake_case consistently. The naming convention is predictable with clear action-object pairs like 'create_index', 'delete_document', 'get_mappings', and 'list_indices'.
16 tools is slightly on the higher side but reasonable for an Elasticsearch MCP server that needs to cover document operations, index management, cluster monitoring, and search functionality. The count feels comprehensive without being excessive for the domain.
The tool set provides complete coverage of Elasticsearch operations including full CRUD for documents (add, update, delete, get via search), index lifecycle management (create, delete, list), cluster monitoring, and advanced operations like bulk processing and query-based updates/deletes. No obvious gaps exist for core Elasticsearch workflows.