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.
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)
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.
Not established by this review
- Authentication, service availability and tool execution were not tested.
- The hosted implementation source and licence were not established.
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.
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