opensearch-mcp-server
Related Servers
Alternatives to opensearch-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides tools to query Elasticsearch indices, retrieve mappings, execute searches, and get cluster health stats.4MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with OpenSearch clusters to monitor cluster health, manage indices, and perform data searches. It provides a standardized interface for real-time OpenSearch operations within MCP-compatible environments like Open WebUI.-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with OpenSearch clusters for searching indices, retrieving mappings, and managing shards through the MCP protocol.Apache 2.0
- AlicenseBqualityDmaintenanceEnables interaction with Elasticsearch clusters for health checks, index management, document CRUD operations, and search via natural language.104 npmMIT
- AlicenseNot gradedqualityDmaintenance* Index Management Tools: * List all indices in OpenSearch cluster * Get index mapping * Get index settings * Cluster Management Tools: * Get cluster health status * Get cluster statistics * Document Tools: * Search documents2MIT
- FlicenseBqualityNot gradedmaintenanceProvides comprehensive tools for managing Elasticsearch clusters, including security management, search operations, and index administration. It enables users to monitor cluster health, handle InfoSec tasks, and execute complex queries using Elasticsearch Query DSL and ES|QL.37-
TDQS
Scored across 4 tools
Each tool targets a distinct OpenSearch resource: indices, index mappings, search results, and shard info. There is no overlap, and the descriptions clearly delineate their purposes.
Most tool names follow a verb-noun pattern (ListIndex, SearchIndex, GetShards), but IndexMappingTool deviates by leading with a noun. The consistent 'Tool' suffix helps, but the mixed pattern is a minor inconsistency.
The 4 tools are well-scoped for an OpenSearch read-only server focusing on index and shard inspection. Each tool has a clear purpose, and the count fits within the ideal 3-15 range.
The tool surface lacks fundamental OpenSearch operations such as creating or deleting indices, indexing, or retrieving documents. This makes the server suitable only for inspection tasks, leaving significant gaps for common workflows.