Elasticsearch MCP Server connects AI agents to Elasticsearch data through the Model Context Protocol, enabling natural language interactions with Elasticsearch indices for querying and analysis. Key features of Elasticsearch MCP Server: - Index discovery and exploration of available indices in your Elasticsearch cluster - Mapping retrieval to understand the structure and fields of your data - Search execution to query documents and retrieve specific data - Shard information access for cluster topology and data distribution details - Support for stdio and streamable-HTTP protocols - Available as a Docker container image from AWS Marketplace Note: This MCP server is deprecated and has been superseded by the Elastic Agent Builder MCP endpoint available in Elastic 9.2.0+ and Elasticsearch Serverless projects.

Elasticsearch MCP Server

> [!CAUTION] > This MCP server is deprecated and will only receive critical security updates going forward. > It has been superseded by the Elastic Agent Builder MCP endpoint, which is available in Elastic 9.2.0+ and Elasticsearch Serverless projects.

Use the Elasticsearch MCP Server for AI Agents

The Elasticsearch MCP Server connects your AI agents to Elasticsearch data using the Model Context Protocol (MCP). It enables natural language interactions with your Elasticsearch indices, allowing agents to query, analyze, and retrieve data without custom APIs.

Follow these steps to deploy and configure the Elasticsearch MCP Server container image from AWS Marketplace.

Before you begin

Before you start, ensure you have:

> [!NOTE] > > These instructions apply to Elasticsearch MCP Server 0.4.0 and later. > For versions 0.3.1 and earlier, refer to the README for v0.3.1.

Deploy the Elasticsearch MCP Server

The Elasticsearch MCP Server is provided as a Docker container image available from AWS Marketplace. You can run it using either the stdio protocol (for direct client connections) or the streamable-HTTP protocol (for web-based integrations).

#### Choose a protocol

The server supports two protocols:

> Note: Server-Sent Events (SSE) is deprecated. Use streamable-HTTP instead.

Configure the stdio protocol

Use the stdio protocol when your MCP client connects directly to the server process.

#### Set environment variables for stdio mode

Set the following environment variables:

#### Run the container in stdio mode

Start the MCP server in stdio mode:

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

#### Configure Claude Desktop

Add this configuration to your Claude Desktop configuration file:

{
  "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": ""
      }
    }
  }
}

Replace ` with your Elasticsearch cluster URL and with your API key.

Configure the streamable-HTTP protocol

Use the streamable-HTTP protocol for web-based integrations or when you need to support multiple concurrent clients.

#### Set environment variables for HTTP mode

Set the same environment variables as the stdio protocol:

#### Run the container in HTTP mode

Start the MCP server in HTTP mode:

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

The streamable-HTTP endpoint is available at http://:8080/mcp`. A health check endpoint is available at