Elasticsearch MCP Server

Elasticsearch is a distributed, RESTful search and analytics engine capable of solving a growing number of use cases.

Tools

Last Updated

Apr 7, 2026

What is the Elasticsearch MCP Server?

The Elasticsearch MCP server gives AI agents structured, permission-aware access to Elasticsearch through the Model Context Protocol. With 39 pre-built actions, agents can read, create, and update Elasticsearch data on behalf of authorized users.

Willow ships the Elasticsearch MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Elasticsearch is being used by every AI agent in your stack.

Tools

Get Cluster Health

Returns the health status of your Elasticsearch cluster. Use this to check if the cluster is operational (green/yellow/red status), monitor shard allocation, and identify potential issues. Useful for monitoring and troubleshooting.

Get Cluster Stats

Returns high-level cluster statistics including node count, shard distribution, index count, document count, storage usage, and more. Use this for capacity planning and monitoring cluster growth.

Get Cluster Settings

Retrieves current cluster-wide settings including persistent and transient settings. Use this to view configuration like shard allocation, routing, discovery settings, and custom cluster properties.

Update Cluster Settings

Updates cluster-wide settings dynamically without requiring a restart. Can set persistent (survives restart) or transient (reset on restart) settings. Use for tuning shard allocation, routing, and other cluster behaviors.

Get Cluster State

Returns comprehensive information about the cluster state including metadata, routing table, nodes, and cluster settings. Warning: can return large responses. Use metrics parameter to filter specific sections.

Get Nodes Info

Returns information about cluster nodes including OS, JVM, thread pools, plugins, and configuration. Useful for understanding cluster topology and node capabilities.

List Indices

Lists all indices in the cluster with key information like health, status, document count, size, and shard count. Use this to discover available indices and monitor their health.

Create Index

Creates a new index with optional settings, mappings, and aliases. Use this to set up new indices with custom shard configuration, analyzers, and field mappings before indexing data.

Delete Index

Permanently deletes an index and all its data. This operation cannot be undone. Use with caution. Supports wildcards to delete multiple indices.

Get Index

Retrieves detailed information about one or more indices including settings, mappings, and aliases. Use this to understand index configuration and structure.

1 2 3 4

1–10 of 39 tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

Set Up Your Elasticsearch MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json

{
  "mcpServers": {
    "willow-elasticsearch": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/elasticsearch"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "willow-elasticsearch": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/elasticsearch"
    }
  }
}

Claude Code

CLI

claude mcp add willow-elasticsearch --transport http https://<org>.mcp-s.com/mcp/mcp/elasticsearch

n8n

HTTP Request Node

{
  "url": "https://<org>.mcp-s.com/mcp/mcp/elasticsearch",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Elasticsearch

Willow adds the layer Elasticsearch and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Elasticsearch MCP Server FAQ

What is the Elasticsearch MCP server?

The Elasticsearch MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Elasticsearch data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Elasticsearch MCP server different from the official one?

The official Elasticsearch MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Elasticsearch MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Elasticsearch MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Elasticsearch, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Elasticsearch actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Elasticsearch MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Elasticsearch MCP locally, you'll see it.

What does the Elasticsearch MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Elasticsearch MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.