Elastic MCP
Related Servers
Alternatives to Elastic MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceConnects agents to Elasticsearch data using the Model Context Protocol, allowing natural language interaction with Elasticsearch indices through tools for listing indices, getting field mappings, performing searches, and viewing shard information.1,413 npmApache 2.0
- AlicenseBqualityDmaintenanceConnects to Elasticsearch databases using the Model Context Protocol, allowing users to query and interact with their Elasticsearch indices through natural language conversations.412 npmApache 2.0
- AlicenseAqualityAmaintenanceFacilitates interaction with Elasticsearch clusters by allowing users to perform index operations, document searches, and cluster management via a Model Context Protocol server and natural language commands.20307Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables secure and efficient interaction with Elasticsearch clusters through the Model Context Protocol, providing tools for data management, search, and export.30 npm1MIT
- AlicenseBqualityDmaintenanceEnables interaction with Elasticsearch clusters for health checks, index management, document CRUD operations, and search via natural language.104 npmMIT
- AlicenseBqualityCmaintenanceConnects agents to Elasticsearch data using the Model Context Protocol, allowing natural language interaction with Elasticsearch indices through MCP Clients like Claude Desktop and Cursor.1135 npm23MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_index_mappings retrieves schema information for a specific index, list_indices enumerates all indices, and search_index performs queries on an index. There is no overlap in functionality, making it easy for an agent to select the correct tool.
All tool names follow a consistent verb_noun pattern (get_index_mappings, list_indices, search_index) with clear, descriptive verbs and nouns. This uniformity enhances readability and predictability.
With only 3 tools, the server feels thin for an Elasticsearch domain, which typically involves more operations like creating/deleting indices, updating mappings, or complex queries. While the tools cover basic inspection and search, the scope is limited.
The tool set is severely incomplete for Elasticsearch operations. It lacks essential CRUD actions such as creating or deleting indices, updating mappings, and handling documents (e.g., index, update, delete). This will cause agent failures when trying to perform common tasks beyond listing and searching.