Elasticsearch MCP server for AI agents

The Elasticsearch MCP Server provides a bridge between Model Context Protocol clients (like Claude Desktop or Cursor) and your Elasticsearch cluster, allowing you to interact with your data through natural language conversations.

Installation

Using the NPM Package

The easiest way to get started with Elasticsearch MCP Server is through the published npm package:

Configure Your MCP Client

Open your MCP Client (such as Claude Desktop), navigate to Settings > Developer > MCP Servers, click "Edit Config" and add:

{
  "mcpServers": {
    "elasticsearch-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@awesome-ai/elasticsearch-mcp"
      ],
      "env": {
        "ES_HOST": "your-elasticsearch-host",
        "ES_API_KEY": "your-api-key"
      }
    }
  }
}

Start a Conversation
- Open a new conversation in your MCP Client
- The server should connect automatically
- Begin asking questions about your Elasticsearch data

Configuration

Authentication Options

You must provide either an API key or username/password combination:

Environment Variable	Description	Required
`ES_HOST`	Elasticsearch URL(s) - single or comma-separated	Yes
`ES_API_KEY`	API key for authentication	No
`ES_USERNAME`	Username for basic authentication	No
`ES_PASSWORD`	Password for basic authentication	No
`ES_CA_CERT`	Path to custom CA certificate	No

Configuring Multiple Nodes

For high availability and load balancing, you can configure multiple Elasticsearch nodes:

{
  "mcpServers": {
    "elasticsearch-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@awesome-ai/elasticsearch-mcp"
      ],
      "env": {
        "ES_HOST": "https://es-node1:9200,https://es-node2:9200,https://es-node3:9200",
        "ES_API_KEY": "your-api-key"
      }
    }
  }
}

The client will automatically handle failover between the configured nodes.

Available Features

Cluster Management

Get Elasticsearch cluster health status with elasticsearch_health

Index Operations

List indices with list_indices (supports regex)
Create indices with create_index (with optional settings and mappings)
Reindex data with reindex (supports optional query and script)

Mapping Management

View field mappings with get_mappings
Create/update mappings with create_mapping

Search & Data Operations

Perform searches with search using Elasticsearch query DSL
Import data in bulk with bulk

Template Management

Create/update templates with create_index_template
View templates with get_index_template
Remove templates with delete_index_template

Example Queries

Here are some natural language queries to try with your MCP Client:

Cluster Management

"What is the health status of my Elasticsearch cluster?"
"How many active nodes are in my cluster?"

Index Operations

"What indices do I have in my Elasticsearch cluster?"
"Create a new index called 'users' with 3 shards and 1 replica."
"Reindex data from 'old_index' to 'new_index'."

Mapping Management

"Show me the field mappings for the 'products' index."
"Add a keyword type field called 'tags' to the 'products' index."

Search & Data Operations

"Find all orders over $500 from last month."
"Which products received the most 5-star reviews?"
"Bulk import these customer records into the 'customers' index."

Template Management

"Create an index template for logs with pattern 'logs-*'."
"Show me all my index templates."
"Delete the 'outdated_template' index template."

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "elasticsearch-mcp" '{"command":"npx","args":["-y","@awesome-ai/elasticsearch-mcp"],"env":{"ES_HOST":"your-elasticsearch-host","ES_API_KEY":"your-api-key"}}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "elasticsearch-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@awesome-ai/elasticsearch-mcp"
            ],
            "env": {
                "ES_HOST": "your-elasticsearch-host",
                "ES_API_KEY": "your-api-key"
            }
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "elasticsearch-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@awesome-ai/elasticsearch-mcp"
            ],
            "env": {
                "ES_HOST": "your-elasticsearch-host",
                "ES_API_KEY": "your-api-key"
            }
        }
    }
}

3. Restart Claude Desktop for the changes to take effect