---
title: "Elastic Agent Builder MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/elastic-agent-builder/
description: "Exposes an Elastic Agent Builder tool catalog to external MCP clients through a chosen Kibana space."
---

# Elastic Agent Builder MCP: review, setup & limitations · Undominated.ai

> Exposes an Elastic Agent Builder tool catalog to external MCP clients through a chosen Kibana space.

[← Explore all mcp servers](/mcp-servers/)

SEARCH AND ANALYTICS / Elastic

# Elastic Agent Builder MCP

Exposes an Elastic Agent Builder tool catalog to external MCP clients through a chosen Kibana space.

 [See setup guidance ↓](#setup)[Original source ↗](https://www.elastic.co/docs/explore-analyze/ai-features/agent-builder/mcp-server)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 1 linked sources
 Publisher Elastic
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“Elastic Agent Builder MCP server”

 [Elastic · upstream description ↗](https://www.elastic.co/docs/explore-analyze/ai-features/agent-builder/mcp-server) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Uses the documented successor to the deprecated standalone Elasticsearch MCP server.
- The setup distinguishes a shared API-key identity from per-user OAuth permissions.
- Elastic’s page says Agent Builder is the MCP server that external hosts call to use Agent Builder tools, including an ES|QL query from Claude Desktop without opening Kibana.
- Those hosts need credentials, either API keys or OAuth 2.1, and some built-in tools are not exposed because their results only the Agent Builder chat can use.

### A good fit for

 - Querying an authorized Elastic data space or using its reviewed Agent Builder tools from an external client.
- Running Elastic Agent Builder tools from an external MCP host that can authenticate to the deployment
- Checking which built-in tools a given stack version actually excludes

### Weigh up before choosing

 - OAuth is documented for Serverless projects; Elastic Stack deployments use the API-key path.
- A shared API key gives callers one shared identity; the tool catalog can include workflows and should not be assumed read-only.
- The page says versions 9.2 to 9.5 do not exclude any built-in tools, so the exclusion behavior is version-specific.
- It does not say the MCP server replaces the in-product chat for tools whose results only that chat can use.
- No licence was stated on this page, and none was inferred.
- This review did not execute the resource.
- The server was not called.
- Some built-in visualization tools are omitted from MCP because their results only work in Elastic Agent Builder chat.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - https://www.elastic.co/docs/explore-analyze/ai-features/agent-builder/mcp-server (setup, access and capability sections)
- https://www.elastic.co/docs/explore-analyze/ai-features/agent-builder/mcp-server
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - The endpoint uses /api/agent_builder/mcp, with /s/{SPACE_NAME} for a custom space.
- Cross-project searches use the default search scope of the selected space, so the MCP URL affects data scope.
- Elastic Agent Builder is documented as the MCP server that external hosts connect to in order to use its tools.
- External hosts need credentials at the endpoint, and the page says to choose API keys or OAuth 2.1 for the deployment.
- Some built-in tools are not available through the MCP server because their results only Agent Builder chat can use. The page also says that in 9.2 to 9.5 the server does not exclude any built-in tools.
- OAuth connections use each consenting user's live project permissions, whereas a shared API key applies one snapshotted identity to every caller.

### Not established by this review

 - Authentication, service availability and tool execution were not tested.
- The hosted implementation source and licence were not established.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://www.elastic.co/docs/explore-analyze/ai-features/agent-builder/mcp-server)
 - Copy the MCP URL from the Agent Builder Tools interface, including the intended Kibana space.
- Configure a limited API key, or register an OAuth application connection on a supported Serverless deployment.

### Before you start

 - An Elastic deployment with Agent Builder and access to the intended tools/data space.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "elastic-agent-builder": {
 "command": "npx",
 "args": [
 "mcp-remote",
 "${KIBANA_URL}/api/agent_builder/mcp",
 "--header",
 "Authorization:${AUTH_HEADER}"
 ],
 "env": {
 "KIBANA_URL": "${KIBANA_URL}",
 "AUTH_HEADER": "ApiKey ${API_KEY}"
 }
 }
 }
} Copy configuration ↗

### Compatibility

A client supporting the documented remote transport and authentication flow. · Configuration example is the API-key page’s mcpServers block, which runs mcp-remote through npx.

### Transports

HTTP

### Remote service / documented account access

 - Uses the Agent Builder tool catalog under API-key or user permissions, including configured workflows.

### Cost model

Elastic deployment, account and tool/service usage determine cost.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Elastic Agent Builder MCP official setup guide ↗](https://www.elastic.co/docs/explore-analyze/ai-features/agent-builder/mcp-server) Checked 2026-10-14 https://www.elastic.co/docs/explore-analyze/ai-features/agent-builder/mcp-server Supports: summary, whySelected, bestFor, limitations, review, compatibility, install, access, transports, configExample

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Algolia MCP Server ↗ Algolia's managed MCP offerings: Public MCP exposes application-scoped search and recommendations on selected indices for customer-facing agents; Productivity MCP gives user-scoped, read-only exploration and analytics; DevEx MCP serves version-matched API client snippets to coding agents without touching data.](/mcp-servers/algolia/)[### Meilisearch MCP ↗ Search and administer Meilisearch indexes, documents, settings and API keys from a local MCP process.](/mcp-servers/meilisearch/)[### OpenSearch MCP Server ↗ Lets an assistant list indices, read mappings, run searches and call any OpenSearch API through one generic tool, against one or several clusters. The Python implementation supports stdio and a streaming transport (SSE and Streamable HTTP) at the pinned revision.](/mcp-servers/opensearch/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
