Catalog / Elasticsearch
Connect Elasticsearch to Claude
PlannedSearch the logs and data in your self-hosted Elasticsearch in plain language – from Claude on the web, on your phone or in your IDE.
Your address for Claudehttps://elasticsearch-acme.xenmcp.com/mcp
Since version 9.2 Elastic ships its own MCP server in Kibana (Agent Builder). On self-managed clusters, however, it is part of the Enterprise licence. If you run Elasticsearch on the free Basic licence, there is no ready MCP server, and Elastic’s earlier open server is deprecated.
For these cases XenMCP plans a server built on the Elasticsearch REST API: you add the address and a read-only API key, XenMCP starts the server in an isolated sandbox and gives you an address with OAuth – everyone signs in as themselves.
Your cluster does not have to be open to the whole internet: XenMCP connects from a fixed IP address.
What you can ask Claude
- Which errors did the
checkoutservice log in the last hour, grouped by message? - Show me the logs around the crash today at 03:12.
- Which indices are there, how large are they, and which fields does
logs-apphave? - How many requests with a 5xx status were there per hour since yesterday?
- Write an ES|QL query for the slowest endpoints and run it.
Typical tools
search- Search documents with Query DSL (hit count capped)
esql- Run ES|QL queries
list_indices- Show indices, size and document count
get_mappings- Show the fields and types of an index
Write, delete, manage indices- Not provided
What you need to connect
- The address of your cluster (
https://es.your-company.com:9200) - An API key with read-only privileges (
read,view_index_metadata) on the indices you choose - XenMCP’s fixed IP address allowed in your firewall or reverse proxy
Security
- Read-only: the server has no write tools and the API key can only read – a mistake on one side still allows no changes.
- The API key’s privileges decide which indices Claude can see.
- No open cluster needed: allow only XenMCP’s fixed IP.
- Everyone signs in as themselves via OAuth; whoever leaves the team loses access without you rotating the key.
- Logs can contain personal data. Results go to your AI client – only allow the indices that are needed.
- The call log keeps only tool, status and duration – no queries and no results.
Good to know
With an Enterprise licence or Elastic Cloud Hosted you already have Elastic’s MCP server in Agent Builder – there our OAuth bridge is enough for per-person sign-in. For Elastic Cloud Serverless, Elastic offers OAuth itself.
Built on
There is no open server for this system yet that meets our criteria. We are building one on the official API.
Frequently asked questions
Do I need an Enterprise licence?
No. This server is meant for clusters on the free Basic licence and only uses the regular REST API.
Which Elasticsearch versions are supported?
Current versions 8 and 9 are planned. ES|QL is available from version 8.11.
Does it work with OpenSearch?
Not decided yet. The search API is similar, but OpenSearch has no ES|QL. Tell us on the waitlist if you use OpenSearch.
Where is my data processed?
The MCP server runs at XenMCP in Germany. Query results go to the AI client you connect – for Claude, that is Anthropic.
When will Elasticsearch be available?
Elasticsearch is planned after the first wave. The waitlist decides the order.
Connect Elasticsearch to Claude?
Join the waitlist. We will get in touch as soon as this server is ready – your interest decides the order.
Join the waitlist