Summary
Index and document administration, searches, and cluster checks run through one server against an OpenSearch cluster.
The 20 tools read and write: they create and delete indices, documents, aliases, and data streams, and delete_by_query removes every document a query matches. general_api_request is an escape hatch to any OpenSearch endpoint without a dedicated tool, and analyze_text shows how an analyzer tokenizes text for debugging.
What it is
An OpenSearch administration server: its 20 tools manage indices, documents, aliases, and data streams, run searches, report cluster health, and pass through arbitrary API calls.
What you get
- Create, list, inspect, and delete indices (create_index, list_indices, get_index, delete_index)
- Index, fetch, search, and delete documents, including delete-by-query (index_document, search_documents, get_document, delete_by_query)
- Manage aliases and data streams (put_alias, list_aliases, create_data_stream, delete_data_stream)
- Check cluster health and statistics (get_cluster_health, get_cluster_stats)
- Debug analysis with analyze_text and reach any endpoint with general_api_request
Requirements
A reachable OpenSearch or Elasticsearch cluster; a cluster name can be passed per call or a default used.
Setup effort
One command plus a key — uvx opensearch-mcp-server, then supply credentials