Happy slice of mcp pizzaMCP.pizza

mcp-server-elasticsearch

MCP.Pizza Chef: elastic

Elastic has marked this one deprecated: it now receives critical security fixes only, and the company points people to the Agent Builder connection built into Elasticsearch 9.2 and later. On an older cluster it still does the job, letting an assistant ask questions of your stored records and get answers back without anyone writing a query. It ships as a container image, needs your cluster address plus a key or a username and password, and works with Claude Desktop, Cursor, and VS Code.

Deprecated · Elastic deprecated it; use Agent Builder in Elasticsearch 9.2+
Data

Use This MCP server To

Search our logs for what happened during last night's outage Ask which stored collection holds the customer records Pull up documents matching a phrase I half remember Summarize what our search records say about a product

README

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:

  • An Elasticsearch cluster (version 8.x or 9.x) accessible from your AWS environment
  • Elasticsearch authentication credentials:
  • Docker installed and running in your AWS environment (for example, on an EC2 instance or in a container service)
  • An MCP client configured (such as Claude Desktop, Cursor, VS Code, or another MCP-compatible tool)
  • Network connectivity between your deployment environment and your Elasticsearch cluster

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).

mcp-server-elasticsearch FAQ

Is this still maintained?
No. Elastic has deprecated it and says only critical security updates will follow.
What should I use instead?
Elastic points to the Agent Builder connection included in Elasticsearch 9.2 and newer, and in Serverless projects.
Which apps does this work in?
Claude Desktop, Cursor, and VS Code are named in the instructions, along with other MCP-capable tools.
Do I need a key?
Yes, either an Elasticsearch key or a username and password, plus the address of your cluster.
Can I use this to search my company's records by just asking?
Yes, that is exactly what it does, as long as your information already lives in Elasticsearch.
How hard is the setup?
It runs as a container, so you need Docker and some comfort with starting one from a terminal.