Elasticsearch
Connect to and interact with an Elasticsearch cluster directly from any MCP client using environment variables for configuration.
Elasticsearch MCP Server
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
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 regexcreate_index: Create Elasticsearch index with optional settings and mappingsreindex: 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 indexcreate_mapping: Create or update mapping structure for an Elasticsearch index
Search & Data Operations
search: Perform an Elasticsearch search with the provided query DSLbulk: Bulk data into an Elasticsearch index
Template Management
create_index_template: Create or update an index templateget_index_template: Get information about index templatesdelete_index_template: Delete an index template
How It Works
- The MCP Client analyzes your request and determines which Elasticsearch operations are needed.
- The MCP server carries out these operations (listing indices, fetching mappings, performing searches).
- 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.
-
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 Configand 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" } } } } -
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(s) - supports single URL or comma-separated multiple URLs (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 |
Multiple URLs Configuration
You can configure multiple Elasticsearch nodes for high availability and load balancing:
{
"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 and load balancing between the configured nodes.
Local Development
[!NOTE] If you want to modify or extend the MCP Server, follow these local development steps.
-
Use the correct Node.js version
nvm use -
Install Dependencies
npm install -
Build the Project
npm run build -
Run locally in Claude Desktop App
- Open Claude Desktop App
- Go to Settings > Developer > MCP Servers
- Click
Edit Configand 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" } } } } -
Run locally in Cursor Editor
- Open Cursor Editor
- Go to Cursor Settings > MCP
- Click
Add new global MCP Serverand 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" } } } } -
Debugging with MCP Inspector
ES_HOST=your-elasticsearch-url ES_API_KEY=your-api-key npm run inspectorThis 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.
Servidores relacionados
Supavec MCP Server
Fetch relevant content from Supavec, a vector database service.
Flexpa FHIR
An MCP server for interacting with FHIR (Fast Healthcare Interoperability Resources) servers, enabling access and search of healthcare data.
Azure TableStore
An MCP server for interacting with Azure Table Storage, requiring an Azure Storage connection string.
GeoServer MCP Server
Connects Large Language Models to the GeoServer REST API, enabling AI assistants to interact with geospatial data and services.
CData API Driver MCP Server
A read-only MCP server for querying live data from various APIs using the CData JDBC Driver for API Driver.
SG Data MCP
Real-time Singapore government data and ACRA company intelligence for AI agents. 13 tools: weather, air quality, dengue clusters, transport, and company verification.
Apple Health MCP
Query Apple Health data using natural language and SQL.
dbt CLI
An MCP server that wraps the dbt CLI, allowing AI agents to interact with dbt projects.
Avro MCP Server by CData
A read-only MCP server for Avro data sources, powered by the CData JDBC Driver.
SupaMCP Server
A runtime-configurable MCP server that turns a Supabase project into an AI-compatible tool interface.
