A Model Context Protocol (MCP) server implementation that provides Elasticsearch and OpenSearch interaction. This server enables searching documents, analyzing indices, and managing cluster through a set of tools.
MCP.Pizza Chef: cr7258
Search systems like Elasticsearch and OpenSearch hold the logs and records many companies run on, and this lets an assistant question them for you: listing what is stored, finding matching documents, checking whether everything is healthy, and adding, updating or removing records on request. Several separate systems can be set up side by side and named, so you can ask about production or staging by name. You supply a login or access key for each one.
Data
Use This MCP server To
Search our logs for errors from the last hour Check whether the search system is healthy right now List what collections of records we actually have Pull up a single record by its identifier Clean out the test records I created yesterday Compare what production holds against staging
README
elasticsearch-mcp-server FAQ
Is this still maintained?
Yes. The project is actively worked on, with changes landing within the last week.
Which apps does it work in?
Claude Desktop is the documented setup, and any other app that speaks the same protocol can use it as well.
Do I need a key?
Yes. You provide either a username and password or an access key for your search system, saved in your app's settings.
Can I use this to search our logs in plain English?
Yes. You describe what you are looking for, and it runs the search and brings back the matching records.
Can it delete things?
Yes. It can create, change and delete both records and whole collections, so give it read-only credentials if that makes you nervous.
Does it work with OpenSearch too?
Yes. Both Elasticsearch and OpenSearch are supported, and you can register several systems and pick between them per question.
How hard is the setup?
You paste a short block into your app's settings with the address and login details, so no programming is required.