elastic-mcp
Related Servers
Alternatives to elastic-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables LLMs to interact with Elasticsearch clusters, allowing them to manage indices and execute search queries using natural language.2-
- 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.20308Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools and resources to interact with Elasticsearch clusters, including listing indices, searching, and retrieving mappings.3MIT
- AlicenseNot gradedqualityDmaintenanceEnables secure and efficient interaction with Elasticsearch clusters through the Model Context Protocol, providing tools for data management, search, and export.53 npm1MIT
- AlicenseAqualityDmaintenanceA comprehensive Model Context Protocol server that integrates Elasticsearch search with file operations, document validation, and version control to transform AI assistants into powerful knowledge management systems.2793 PyPI27MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables interaction with Elasticsearch and OpenSearch clusters for searching documents and managing indices. It provides tools for cluster health monitoring, index configuration, and general API requests.16Apache 2.0
TDQS
Scored across 14 tools
The tool set maps cleanly to distinct Elasticsearch endpoints: cluster, nodes, shards, indices, documents, mappings, settings, aliases, and Kibana objects. Search, count, and esql overlap somewhat as query paths, but their descriptions clearly differentiate Query DSL hits/aggregations, simple counts, and ES|QL pipelines.
Naming is mostly predictable: list_* enumerates cluster resources, get_* fetches specific objects or metadata, cluster_* covers cluster-level views, and search/count/esql are self-explanatory actions. The mix of list_/get_ and bare verbs is a minor inconsistency, but it is still readable and not chaotic.
14 tools is well within the ideal range and each tool covers a major Elasticsearch operation area: cluster, nodes, shards, indices, documents, queries, and Kibana. No tool feels redundant or excessive for the apparent read/query/monitoring scope.
As a read/query/monitoring surface, it covers the main workflows: cluster health and stats, node/shards inspection, index metadata, aliases, mappings, documents, multiple query languages, and Kibana saved objects. The obvious gap is the absence of write/management tools such as create, update, or delete, so the server is complete only for read-oriented use.