Fire in da houseTop Tip:Paying $100+ per month for Perplexity, MidJourney, Runway, ChatGPT and other tools is crazy - get all your AI tools in one site starting at $15 per month with Galaxy AI Fire in da houseCheck it out free

elasticsearch-mcp

MCP.Pizza Chef: awesimon

The Elasticsearch MCP server connects MCP clients to Elasticsearch clusters, enabling natural language interaction with indices. It supports cluster health monitoring, index listing, creation, and management, as well as search and indexing operations. This server facilitates seamless integration of Elasticsearch data into AI workflows, allowing users to query and manipulate data through conversational interfaces.

Use This MCP server To

Monitor Elasticsearch cluster health status in real time List and filter Elasticsearch indices using regex Create and configure new Elasticsearch indices Perform natural language search queries on Elasticsearch data Index documents into Elasticsearch via conversational commands Manage Elasticsearch indices including deletion and updates Integrate Elasticsearch data into AI-driven workflows and agents

README

Elasticsearch MCP Server

English | δΈ­ζ–‡

smithery badge

MCP Server for connecting to your Elasticsearch cluster directly from any MCP Client (like Claude Desktop, Cursor).

This server connects agents to your Elasticsearch data using the Model Context Protocol. It allows you to interact with your Elasticsearch indices through natural language conversations.

Demo

Elasticsearch MCP Demo

Feature Overview

Available Features

Cluster Management
  • elasticsearch_health: Get Elasticsearch cluster health status, optionally including index-level details
Index Operations
  • list_indices: List available Elasticsearch indices, support regex
  • create_index: Create Elasticsearch index with optional settings and mappings
  • reindex: Reindex data from a source index to a target index with optional query and script
Mapping Management
  • get_mappings: Get field mappings for a specific Elasticsearch index
  • create_mapping: Create or update mapping structure for an Elasticsearch index
Search & Data Operations
  • search: Perform an Elasticsearch search with the provided query DSL
  • bulk: Bulk data into an Elasticsearch index
Template Management
  • create_index_template: Create or update an index template
  • get_index_template: Get information about index templates
  • delete_index_template: Delete an index template

How It Works

  1. The MCP Client analyzes your request and determines which Elasticsearch operations are needed.
  2. The MCP server carries out these operations (listing indices, fetching mappings, performing searches).
  3. The MCP Client processes the results and presents them in a user-friendly format.

Getting Started

Prerequisites

  • An Elasticsearch instance
  • Elasticsearch authentication credentials (API key or username/password)
  • MCP Client (e.g. Claude Desktop, Cursor)

Installation & Setup

Using the Published NPM Package

Tip

The easiest way to use Elasticsearch MCP Server is through the published npm package.

  1. Configure MCP Client

    • Open your MCP Client. See the list of MCP Clients, here we are configuring Claude Desktop.
    • Go to Settings > Developer > MCP Servers
    • Click Edit Config and add a new MCP Server with the following configuration:
    {
      "mcpServers": {
        "elasticsearch-mcp": {
          "command": "npx",
          "args": [
            "-y",
            "@awesome-ai/elasticsearch-mcp"
          ],
          "env": {
            "ES_HOST": "your-elasticsearch-host",
            "ES_API_KEY": "your-api-key"
          }
        }
      }
    }
  2. Start a Conversation

    • Open a new conversation in your MCP Client.
    • The MCP server should connect automatically.
    • You can now ask questions about your Elasticsearch data.

Configuration Options

The Elasticsearch MCP Server supports configuration options to connect to your Elasticsearch:

Note

You must provide either an API key or both username and password for authentication.

Environment Variable Description Required
ES_HOST Your Elasticsearch instance URL (also supports legacy HOST) Yes
ES_API_KEY Elasticsearch API key for authentication (also supports legacy API_KEY) No
ES_USERNAME Elasticsearch username for basic authentication (also supports legacy USERNAME) No
ES_PASSWORD Elasticsearch password for basic authentication (also supports legacy PASSWORD) No
ES_CA_CERT Path to custom CA certificate for Elasticsearch SSL/TLS (also supports legacy CA_CERT) No

Local Development

Note

If you want to modify or extend the MCP Server, follow these local development steps.

  1. Use the correct Node.js version

    nvm use
  2. Install Dependencies

    npm install
  3. Build the Project

    npm run build
  4. Run locally in Claude Desktop App

    • Open Claude Desktop App
    • Go to Settings > Developer > MCP Servers
    • Click Edit Config and add a new MCP Server with the following configuration:
    {
      "mcpServers": {
        "elasticsearch-mcp": {
          "command": "node",
          "args": [
            "/path/to/your/project/dist/index.js"
          ],
          "env": {
            "ES_HOST": "your-elasticsearch-host",
            "ES_API_KEY": "your-api-key"
          }
        }
      }
    }
  5. Run locally in Cursor Editor

    • Open Cursor Editor
    • Go to Cursor Settings > MCP
    • Click Add new global MCP Server and add a new MCP Server with the following configuration:
    {
      "mcpServers": {
        "elasticsearch-mcp": {
          "command": "node",
          "args": [
            "/path/to/your/project/dist/index.js"
          ],
          "env": {
            "ES_HOST": "your-elasticsearch-host",
            "ES_API_KEY": "your-api-key"
          }
        }
      }
    }
  6. Debugging with MCP Inspector

    ES_HOST=your-elasticsearch-url ES_API_KEY=your-api-key npm run inspector

    This will start the MCP Inspector, allowing you to debug and analyze requests. You should see:

    Starting MCP inspector...
    βš™οΈ Proxy server listening on port 6277
    πŸ” MCP Inspector is up and running at http://127.0.0.1:6274 πŸš€

Example Queries

Tip

Here are some natural language queries you can 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."

If you encounter issues, feel free to open an issue on the GitHub repository.

elasticsearch-mcp FAQ

How do I connect the Elasticsearch MCP server to my cluster?
Configure the server with your Elasticsearch cluster endpoint and credentials to establish a secure connection.
Can I perform search queries using natural language?
Yes, the server supports natural language queries to search Elasticsearch indices directly.
Does the server support index management operations?
Yes, you can list, create, update, and delete indices through the MCP interface.
How does the server handle cluster health monitoring?
It provides real-time cluster health status, including optional index-level details.
Is authentication supported for secure access?
Yes, the server supports authentication mechanisms to securely connect to your Elasticsearch cluster.
Can this server be used with multiple MCP clients?
Yes, it is designed to work seamlessly with any MCP client like Claude Desktop or Cursor.
What LLM providers are compatible with this server?
It works with OpenAI, Anthropic Claude, and Google Gemini models through MCP clients.
How do I handle large result sets from Elasticsearch queries?
The server supports pagination and filtering to manage large data responses efficiently.