Elastic’s MCP Bridge to Elasticsearch Is Already Closed

What it does

This Rust-based server implements the Model Context Protocol to let AI agents inspect and query Elasticsearch indices using plain English. It exposes a handful of tools—list_indices, search, esql, and a few others—so an agent can discover schemas and run DSL or ES|QL queries without custom API glue. It ships as a Docker image and speaks both stdio and streamable-HTTP.

The interesting bit

The whole project is already deprecated. Elastic points users to the Agent Builder MCP endpoint in Elastic 9.2.0+ instead, making this repo a snapshot of a transition period rather than a destination.

Key highlights

• Deprecated with only critical security updates remaining; superseded by Elastic Agent Builder.
• Supports stdio and streamable-HTTP transports, with legacy SSE explicitly dropped.
• Exposes five tools: list_indices, get_mappings, search, esql, and get_shards.
• Runs as a container image distributed via AWS Marketplace.
• Credentials live strictly in environment variables; the server never persists them to disk.

Caveats

• Elastic has deprecated the project and will only ship critical security fixes.
• Requires an existing Elasticsearch 8.x or 9.x cluster and an AWS-flavored deployment environment.

Verdict

Worth a look if you are maintaining an existing integration or studying how to build an MCP server for a document store, but new projects should head straight to Elastic Agent Builder. Everyone else can treat this as a reference implementation with an expiration date.