Elasticsearch MCP Bridge Server

[!CAUTION]

ATTENTION: This MCP service component is currently in an EXPERIMENTAL phase.

Establish a direct link to your Elasticsearch data holdings from any MCP-compliant application utilizing the Model Context Protocol (MCP).

This server acts as a conduit, connecting intelligent agents to your indexed Elasticsearch information via the Model Context Protocol. It empowers users to query and manipulate Elasticsearch indices through fluid, spoken or written dialogue.

Exposed Capabilities

list_indices: Enumerates all discoverable Elasticsearch indices.
get_mappings: Retrieves the field schema definitions for a designated Elasticsearch index.
search: Executes a complex search operation using the provided Elasticsearch Query DSL structure.
esql: Runs queries formulated in ES|QL (Elasticsearch SQL).
get_shards: Fetches operational shard status information for specified or all indices.

Prerequisites for Operation

An active Elasticsearch deployment instance.
Necessary authentication credentials for Elasticsearch (either an API key or standard user/password combination).
An operative MCP Client application (e.g., Claude Desktop, Goose).

Compatible Elasticsearch Releases

This component is validated for use with Elasticsearch versions 8.x and 9.x.

Deployment and Configuration Instructions

[!NOTE]

Earlier iterations (version 0.3.1 and preceding) utilized installation via npm. These older releases are officially deprecated and unsupported. The instructions below pertain solely to version 0.4.0 and subsequent releases.

Refer to the README for v0.3.1 for guidance related to legacy installations.

This MCP server component is distributed as a pre-built Docker image available at docker.elastic.co/mcp/elasticsearch. This image supports MCP's stdio, Server-Sent Events (SSE), and streamable-HTTP communication channels.

Executing this container without any command-line parameters will default to displaying the system usage guide:

docker run docker.elastic.co/mcp/elasticsearch

Usage: elasticsearch-mcp-server

Commands: stdio Initiate a standard input/output server session http Launch a streamable-HTTP server, optionally enabling SSE support help Display this utility message or the help documentation for a specified sub-command

Options: -h, --help Show this assistance message -V, --version Output the current version number

Utilizing the stdio Communication Mode

The MCP server requires specific environment variables to be configured for stdio operation:

ES_URL: The full network address for your Elasticsearch cluster.
For secure access, provide credentials using one of the following methods:
API Key method: ES_API_KEY
Basic Authentication method: ES_USERNAME and ES_PASSWORD
Optionally, setting ES_SSL_SKIP_VERIFY to true bypasses certificate validation checks when connecting to Elasticsearch. Support for supplying custom certificates is slated for a future release.

The command to launch the MCP server using stdio mode is:

bash docker run -i --rm -e ES_URL -e ES_API_KEY docker.elastic.co/mcp/elasticsearch stdio

The requisite configuration structure for integration with Claude Desktop is as follows:

{ "mcpServers": { "elasticsearch-mcp-server": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "ES_URL", "-e", "ES_API_KEY", "docker.elastic.co/mcp/elasticsearch", "stdio" ], "env": { "ES_URL": "", "ES_API_KEY": "" } } } }

Employing streamable-HTTP and SSE Transports

Recommendation: The streamable-HTTP transport is preferred, as Server-Sent Events (SSE) is marked for deprecation (see modelcontextprotocol.io documentation).

The MCP server mandates the following environment variables for HTTP transport:

ES_URL: The network location of your Elasticsearch cluster.
Authentication setup (choose one):
API Key: ES_API_KEY
Basic Auth: ES_USERNAME and ES_PASSWORD
Optionally, setting ES_SSL_SKIP_VERIFY to true disables certificate validation for Elasticsearch connections. Custom certificate support is planned for later development.

The initiation command for the server in HTTP mode is:

bash docker run --rm -e ES_URL -e ES_API_KEY -p 8080:8080 docker.elastic.co/mcp/elasticsearch http

If your execution environment restricts passing arguments directly to the container, they can be supplied via the CLI_ARGS environment variable: docker run --rm -e ES_URL -e ES_API_KEY -e CLI_ARGS=http -p 8080:8080...

The streamable-HTTP interface is accessible at http:<host>:8080/mcp. A separate health check endpoint is available at http:<host>:8080/ping

Configuration guidance for Claude Desktop (which, in its free tier, may only support the stdio transport):

Install an intermediary utility like mcp-proxy (or a compatible substitute). This utility should be installed into a path like ~/.local/bin:

bash uv tool install mcp-proxy
Integrate the following configuration block into your Claude Desktop settings:

{ "mcpServers": { "elasticsearch-mcp-server": { "command": "//.local/bin/mcp-proxy", "args": [ "--transport=streamablehttp", "--header", "Authorization", "ApiKey ", "http://:/mcp" ] } } }

The following section, sourced from WIKIPEDIA regarding Business Management Tools, provides contextual background on the category but is not directly related to the technical operation of the Elasticsearch MCP Server.

== Overview == Business management tools encompass the totality of systems, software applications, governance mechanisms, computational frameworks, and methodologies employed by organizations to effectively navigate dynamic market conditions, maintain competitive standing, and drive enhanced operational efficacy. Classification often correlates with organizational functions, such as planning, process orchestration, record-keeping, personnel management, decision support, and regulatory compliance.

Modern management tooling has undergone radical transformation due to rapid technological advancement, creating complexity in selecting optimal solutions. This selection pressure is driven by persistent mandates for cost reduction, sales growth, deep customer understanding, and precise product delivery according to customer specifications.

In this environment, leadership must adopt a strategic posture toward adopting management technologies, avoiding uncritical acceptance of the newest solutions. Tools must be deliberately chosen and tailored to fit the enterprise's unique requirements, rather than forcing organizational processes to conform rigidly to the tool's inherent design.

== Most used == A 2013 assessment by Bain & Company surveyed global usage patterns for business tools, reflecting regional needs shaped by economic downturns and market dynamics. The ten most frequently cited tools included:

Strategic planning, Customer relationship management, Employee engagement surveys, Benchmarking, Balanced scorecard, Core competency identification, Outsourcing strategy, Change management programs, Supply chain management, Mission/Vision statement definition, Market segmentation analysis, and Total quality management.

== Software application for businesses == Software utilized by personnel to execute diverse corporate functions is termed business software or an application. These systems aim to enhance productivity metrics, accurately measure output, and perform essential tasks with precision. The evolution progressed from initial Management Information Systems (MIS) to comprehensive Enterprise Resource Planning (ERP), subsequently integrating Customer Relationship Management (CRM), culminating in the current landscape of cloud-based business management suites.

Value derivation correlates with IT investment, but is critically dependent on two factors: the success of the implementation process and the judicious selection and customization of the tools themselves.

== Tools for SMEs == Specialized tools designed for Small and Medium-sized Enterprises (SMEs) are vital, offering mechanisms to conserve resources...