Can AI agents automate Elasticsearch?

Elasticsearch is automatable today through its public REST API and a first-party Kibana Agent Builder MCP server. This record is Elasticsearch plus that Agent Builder MCP path. It is not Datadog, Splunk, or Grafana. Elasticsearch exposes REST APIs that the UI uses and that callers can invoke directly on Elastic Cloud Serverless and Elastic Stack. Auth is API key (Authorization: ApiKey), HTTP Basic, or Bearer tokens. Official clients include the Java API Client and the Python client, which cover the Elasticsearch API surface. Coverage is partial because Kibana Agent Builder and some Cloud/Kibana actions sit outside the Elasticsearch REST contract. The current first-party MCP is Agent Builder at {KIBANA_URL}/api/agent_builder/mcp, or {KIBANA_URL}/s/{SPACE_NAME}/api/agent_builder/mcp for a custom space. Elastic marks it Generally available on Serverless and on Elastic Stack since 9.3, Preview in 9.2. MCP hosts authenticate with API keys on Stack and Serverless, or OAuth 2.1 on Serverless only. Elastic's AI-features page recommends Agent Builder for 9.2+ and Serverless; elastic/mcp-server-elasticsearch is documented only as a limited fallback for older versions without Agent Builder and is not treated here as the current first-party path. Self-managed bin/ command-line tools exist for certificates, users, and enrollment; they are not available on Elastic Cloud Hosted or Serverless and are not a general query CLI. iPaaS connectors were not opened. Computer-use viability is unassessed. API scores 8 and is the best path because it does not require Kibana 9.2+/9.3 or a Serverless OAuth client.

Best path today: api · Overall automatability: 8/10