Summary
The cluster answers questions and accepts changes on the same connection.
Read-only Elasticsearch servers stop at search. This one carries the writes too — bulk operations, update by query, index management — which is what turns 'find the bad documents' into 'and fix them'.
What it is
A TypeScript MCP server over Elasticsearch. It carries full CRUD for documents and indices, bulk operations in a single API call, updates and deletes driven by a query, and the cluster reads — health, shards and templates.
What you get
- Elasticsearch DSL queries with highlighting, against any index
- Documents created, read, updated and deleted
- Indices created and managed
- Many operations sent in one bulk API call
- Documents updated or removed by query rather than one id at a time
- Cluster health, shard state and index templates read
Requirements
An Elasticsearch cluster reachable at ES_URL, with ES_API_KEY and ES_VERSION. Install with npm install -g @octodet/elasticsearch-mcp, or run it through npx.
Setup effort
One command plus a key — npm install -g @octodet/elasticsearch-mcp, then supply credentials