SEARCH AND ANALYTICS / Elastic
Elastic Agent Builder MCP
Exposes an Elastic Agent Builder tool catalog to external MCP clients through a chosen Kibana space.
“Elastic Agent Builder MCP server”
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.
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.
- 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}"
}
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://www.elastic.co/docs/explore-analyze/ai-features/agent-builder/mcp-server
Supports: summary, whySelected, bestFor, limitations, review, compatibility, install, access, transports, configExample