Elastic Agent Builder MCP server

The Model Context Protocol (MCP) server provides a standardized interface for external MCP hosts to access Elastic Agent Builder tools. For example, you can run an ES|QL query against your data from Claude Desktop without opening Kibana.

Note

On this page, Elastic Agent Builder acts as the MCP server: external MCP hosts connect to it to use your Elastic Agent Builder tools. To instead let your agents use tools hosted on an external MCP server, refer to Model Context Protocol (MCP) tools in Elastic Agent Builder.

MCP server endpoint

The MCP server is available at the following endpoint:

{KIBANA_URL}/api/agent_builder/mcp

If you use a custom Kibana space, include the space ID in the endpoint path:

{KIBANA_URL}/s/{SPACE_ID}/api/agent_builder/mcp

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability Generally available This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. If you authenticate with OAuth, don't build this URL yourself. Use the MCP server URL shown in your OAuth client's details. The client works only with that URL, not with the endpoint of any other space.

Tip

You can copy the MCP server URL for the current space in the Tools GUI. Refer to MCP server access in the Tools GUI.

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Preview in 9.2 This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Copy MCP Server URL on the Tools page doesn't include the space ID. Refer to the known issue.

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability Generally available This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. For setup instructions for specific MCP hosts, including prebuilt Elastic connectors in their directories, refer to Connect an MCP host to Elastic Agent Builder.

Authentication and configuration

External MCP hosts need credentials to reach the MCP server endpoint. The way that you configure your MCP server depends on your authentication method. Choose API keys or OAuth 2.1 based on your deployment type and use case.

Use one of the following authentication paths:

API key authentication
OAuth 2.1 authentication using an application connection Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability Generally available This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

The following table compares the two paths.

Consideration	API key	OAuth
Supported platforms	Elastic Stack deployments and Serverless projects	Serverless projects only Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability Generally available This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments.
Best for	Automation, unattended access, and shared machine-to-machine use	Interactive MCP hosts acting on behalf of a person (Claude Desktop, Cursor), including teams that share one client
Multi-user access	One shared key means one shared identity; all callers act with the same permissions	One client registration serves many users. Each person consents separately and gets their own connection, acting with their own permissions and revocable individually
Identity	The key's snapshotted permissions	The consenting user; permissions are the user's live permissions in the project
Credential lifetime	Long-lived until the key expires or is revoked	Short-lived tokens, refreshed automatically unless revoked. Require a new connection if unused for 30+ days.
Setup	Generate a key and add it to the host configuration	Register an MCP client, then consent in the browser
Elastic Agent Builder tools through MCP	Built-in and custom tools, including Elastic Workflows	Built-in and custom tools, limited by the authorizing user's permissions

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Planned We plan to add this functionality in a future Elastic Stack update. Subject to changes. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability Generally available This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. Some built-in tools aren't available through the MCP server, mostly because they return results that only Elastic Agent Builder chat can use, such as platform.core.create_visualization and most cases tools. The built-in tools reference notes which of the documented tools aren't available.

In 9.2 to 9.5, the MCP server doesn't exclude any built-in tools.

Use tools with data from multiple projects

When you have projects linked through cross-project search, tool calls use the default cross-project search scope for the space in the MCP URL. Requests without /s/<space-id> use the default space.