Vector Databases · elastic

mcp-server-elasticsearch

mcp-server-elasticsearch is a Docker-based MCP (Model Context Protocol) server that connects AI agents to Elasticsearch clusters, enabling natural language queries and data analysis. However, the project is officially deprecated as of its latest release, with users directed to Elastic Agent Builder as the successor.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/elastic/mcp-server-elasticsearch

685

GitHub stars

141

Forks

Rust

Primary language

Apache-2.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	elastic/mcp-server-elasticsearch
Owner	elastic
Primary language	Rust
License	Apache-2.0 — OSI-approved
Stars	685
Forks	141
Open issues	15
Latest release	v0.4.6 (2025-10-24)
Last updated	2026-07-01
Source	https://github.com/elastic/mcp-server-elasticsearch

What mcp-server-elasticsearch is

A Rust-based MCP server exposing Elasticsearch functionality via stdio and streamable-HTTP protocols, supporting API key and basic authentication. The server is stateless, containerized, and designed for direct integration with MCP clients (Claude Desktop, Cursor, VS Code). Deprecation status signals end-of-life except for critical security patches.

Quickstart

Get the mcp-server-elasticsearch source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/elastic/mcp-server-elasticsearch.git2cd mcp-server-elasticsearch3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Proof-of-Concept AI Agent Integration

Quickly prototype AI agents that query Elasticsearch indices via natural language without custom API development. Ideal for teams piloting LLM + search integrations before committing to long-term solutions.

Development and Testing Environments

Use in non-production labs or internal tools where Elasticsearch MCP connectivity is needed short-term. Deprecation status is acceptable for ephemeral or experimental deployments.

Elasticsearch 8.x/9.x Integration Testing

Test MCP protocol compatibility and Elasticsearch query execution patterns with existing clusters. Useful for teams validating future Elastic Agent Builder migrations.

Implementation considerations

Docker container image sourced from AWS Marketplace; confirm image availability and pull access in your environment.
Requires direct network connectivity from deployment host to Elasticsearch cluster (8.x or 9.x); validate security group, firewall, and VPC routing rules.
Credentials (API keys or username/password) passed via environment variables; use AWS Secrets Manager or similar for production secret rotation.
Two protocols (stdio and streamable-HTTP) have different trade-offs: stdio for direct client connections; HTTP for concurrency and web integration.
Health check endpoint (`/ping`) available only in HTTP mode; monitor container logs and Elasticsearch connectivity separately for stdio deployments.

When to avoid it — and what to weigh

Production Workloads — Deprecated status with security-only updates means no feature improvements, bug fixes, or version bumps. Production deployments should migrate to Elastic Agent Builder (Elasticsearch 9.2.0+).
Long-Term Maintenance Requirements — No active development post-deprecation. If your roadmap spans 12+ months, expect no improvements and potential incompatibility with future Elasticsearch releases.
Complex Elasticsearch Workflows — Limited by MCP protocol scope. Advanced use cases (custom aggregations, index management, cluster administration) may exceed the server's capabilities.
Enterprise Compliance Requirements — Unknown security audit trail, compliance certifications, or support SLAs. Deprecated status makes vendor support unavailable.

License & commercial use

Apache License 2.0 (Apache-2.0). Permissive OSI-approved license permitting commercial use, modification, and distribution with Apache 2.0 terms (liability disclaimer, patent grant).

Apache 2.0 permits commercial use. However, deprecation status and security-only support posture make it unsuitable for production commercial deployments. Organizations should not rely on this for revenue-critical services. Elastic Agent Builder is Elastic's supported commercial alternative.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Stale
Documentation	Adequate
License clarity	Clear
Deployment complexity	Moderate
DEV.co fit	Possible
Assessment confidence	High

Security considerations

Credentials passed via environment variables (not persisted to disk) is sound. HTTPS to Elasticsearch supported when URL uses https://. No data stored locally in container. Unknown: SSL/TLS default behavior, whether `ES_SSL_SKIP_VERIFY` defaults to true or false, security audit history, or CVE response process post-deprecation. Skip SSL verification only in non-production. Consider that deprecation status may delay or prevent security patch releases.

Alternatives to consider

Elastic Agent Builder MCP Endpoint

Official Elastic successor, available in Elasticsearch 9.2.0+. Actively maintained, vendor-supported, recommended for production migrations.

LangChain / LlamaIndex Elasticsearch Connectors

Framework-native integrations with better long-term support and feature parity. More flexible for complex LLM workflows than MCP protocol constraint.

Custom REST API + MCP Bridge

Build a lightweight MCP wrapper over Elasticsearch REST API to retain control over deprecation risk and feature roadmap.

Software development agency

Build on mcp-server-elasticsearch with DEV.co software developers

This project is deprecated. Consider Elastic Agent Builder (Elasticsearch 9.2.0+) for production, or discuss custom MCP/REST solutions with our team.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

anysearch-mcp-server apify-mcp-server firecrawl-mcp-server

Related on DEV.co

Explore the category and the services that help you build with it.

Vector Databases AI Application Development API Development Cloud Deployment Talk to DEV.co

mcp-server-elasticsearch FAQ

Is this project still maintained?

No. It is officially deprecated as of v0.4.6 (2025-10-24). Only critical security updates will be released. Elastic recommends migrating to Elastic Agent Builder.

What Elasticsearch versions does it support?

Elasticsearch 8.x and 9.x. Elasticsearch Serverless projects are also supported via Elastic Agent Builder (the recommended path forward).

Can I use this in production?

Not recommended. Deprecation status means no feature improvements, bug fixes, or future version compatibility. Use Elastic Agent Builder for production deployments.

Do I need Docker to run this?

Yes. The server is distributed as a Docker container image from AWS Marketplace. No binary releases or native executables are documented.

Work with a software development agency

DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If mcp-server-elasticsearch is part of your vector databases roadmap, our team can implement, customize, migrate, and maintain it.

Evaluating Elasticsearch + AI Integration?

This project is deprecated. Consider Elastic Agent Builder (Elasticsearch 9.2.0+) for production, or discuss custom MCP/REST solutions with our team.

Talk to DEV.co Schedule a Consultation