Elastic Agent Builder MCP server
The MCP server built into Kibana's Elastic Agent Builder, which Elastic names as the replacement for its standalone Elasticsearch MCP server.
What it does
The MCP server built into Kibana's Elastic Agent Builder, which Elastic names as the replacement for its standalone Elasticsearch MCP server. An external MCP client connects to the endpoint at your Kibana URL under /api/agent_builder/mcp (with a space ID for non-default spaces) and can call Agent Builder tools, such as running an ES|QL query, plus custom tools and Elastic Workflows you define. Clients authenticate with an Elasticsearch API key, or on Serverless projects with OAuth 2.1 so each user acts with their own permissions. Some built-in tools that only work inside Agent Builder chat are left out.
Capabilities
- Run ES|QL queries against Elasticsearch data from an MCP client
- Call built-in and custom Agent Builder tools
- Run Elastic Workflows exposed as tools
- Scope tool calls to a Kibana space
Details
| Fact | Value | Source |
|---|---|---|
| Type | MCP server | |
| Tool | Elasticsearch | |
| Publisher | Elastic | source |
| Official status | OfficialElastic's own documentation | source |
| Connection | Remote (hosted, you connect over the internet) | source |
| Can change data | Not stated in its documentation | |
| Needs an API key or sign-in | Yes | source |
| Platforms | Not stated in its documentation | |
| AI clients | Claude Desktop, Cursor, Visual Studio Code | source |
| Licence | Not stated in its documentation | |
| Pricing | Not stated in its documentation | |
| Activity | No commit dataDownload data not available (not on npm or PyPI) | |
| Links | Website |
Sources
- Web pageelastic.co · Backs: AI clients, Connection, Needs an API key or sign-in, Official status, PublisherNov 12, 2026