# Elastic Agent Builder MCP Server [Official] [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://www.elastic.co/docs/solutions/search/agent-builder/mcp-server  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/elastic-agent-builder-mcp

## Description
Elastic's official MCP server, built into Kibana's Agent Builder (Elastic 9.2+ and Elasticsearch Serverless). Exposes your Agent Builder tools, including Elasticsearch search and ES|QL queries, to MCP clients at {KIBANA_URL}/api/agent_builder/mcp, with API key or OAuth access. It replaces the deprecated elastic/mcp-server-elasticsearch.

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://www.elastic.co/docs/deploy-manage/app-connections/connect-mcp-host), copied verbatim. Run them in order; they are not an mcpServers config.

MCP_SERVER_URL is {KIBANA_URL}/api/agent_builder/mcp (or /s/{SPACE_ID}/api/agent_builder/mcp). Needs Elastic 9.2+ or a Serverless project.

1. Add to Claude Code:

```sh
claude mcp add --transport http --client-id {CLIENT_ID} kibana-mcp {MCP_SERVER_URL}
```

## Documentation

## What Elastic Agent Builder MCP Server does

Elastic Agent Builder MCP Server exposes tools configured in Kibana's Agent Builder through the Model Context Protocol. Its documented capabilities include Elasticsearch search and ES|QL query access, allowing compatible MCP clients to use Elastic data tools from an agent workflow.

The server is part of Kibana rather than a separate Elasticsearch MCP process. It is available with Elastic 9.2 and later and with Elasticsearch Serverless. The service replaces the deprecated `elastic/mcp-server-elasticsearch` server.

## How it works

MCP clients connect to the Agent Builder endpoint hosted by Kibana:

```text
{KIBANA_URL}/api/agent_builder/mcp
```

Replace `{KIBANA_URL}` with the URL of the Kibana instance that contains the Agent Builder configuration. Once connected, the client can access the Agent Builder tools exposed through that instance, including Elasticsearch search and ES|QL query tools.

Access is authorized with either an API key or OAuth. The connection therefore uses the security and access controls associated with the Kibana deployment rather than a standalone local process.

## Setup and configuration

Use an Elastic deployment that provides Kibana Agent Builder on Elastic 9.2 or later, or use Elasticsearch Serverless. In the MCP client, configure a connection to the Kibana URL followed by `/api/agent_builder/mcp`.

Provide authentication using one of the supported methods:

- An Elastic API key
- OAuth access

The endpoint is hosted by Kibana, so the client must be able to reach that Kibana URL and the credentials must grant the access required by the Agent Builder tools being used.

## Tools and capabilities

The exposed tool set is based on the tools available through Kibana's Agent Builder. Supported data operations include:

- Searching Elasticsearch data
- Running ES|QL queries
- Making Agent Builder tools available to MCP-compatible clients

The server is suited to agents that need Elastic search and query functionality without using the deprecated standalone Elasticsearch MCP server.

## Limitations and notes

Availability depends on the Elastic platform and version: use Elastic 9.2 or later or Elasticsearch Serverless with Agent Builder. The endpoint exposes Agent Builder tools rather than an independently defined tool catalog. Access also depends on valid API-key or OAuth authorization and connectivity to the Kibana host.

_Full upstream README: https://allmcps.com/mcp/elastic-agent-builder-mcp/readme_