X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Elasticsearch to Claude

Connect Claude Web, Desktop and Cowork to Elasticsearch MCP. Search for documents with error status, create a new index named 'projects', and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Elasticsearch logoElasticsearch
Api KeyBasic

Elasticsearch is a distributed, RESTful search and analytics engine for all types of data. It delivers fast, scalable search and powerful analytics across massive datasets.

4 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Elasticsearch account to Claude via Composio Connect, enabling it to search for documents with error status, create a new index named 'projects', update all records in 'users' index, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Elasticsearch with

Claude CodeCursorChatGPTAntigravityOpenAI Agents SDKClaude Agent SDKCodexGrok BuildVS CodeOpenCodeOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

Connecting Elasticsearch to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Elasticsearch account

Back in Claude, ask it to connect to Elasticsearch or give it any Elasticsearch-related task.

For example, ask Claude to:

  • "Search for documents with error status"
  • "Create a new index named 'projects'"
  • "Update all records in 'users' index"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Elasticsearch account is ready to use.

What is the Elasticsearch Claude Connector, and what's possible with it?

The Elasticsearch MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Elasticsearch account. It provides structured and secure access so your agent can perform Elasticsearch operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for Elasticsearch?

The connector can show as connected, but Claude must use it in each Elasticsearch conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Elasticsearch again.

2. Why does Claude show an MCP server error before Elasticsearch connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Elasticsearch.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Elasticsearch.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Elasticsearch authorization link not work?

The Composio connector is one server. Your Elasticsearch account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Elasticsearch connection.
  • Composio creates a fresh Elasticsearch authorization link.
  • Open that link in your browser and finish the Elasticsearch sign-in.

4. Why do Elasticsearch actions fail after they worked before?

The Elasticsearch connection can expire or lose permission.

  • Ask Claude to inspect the Elasticsearch connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Elasticsearch account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Elasticsearch.
  • If the action still fails with a permission error, check that the connected account has that permission in Elasticsearch itself.

5. How do I switch to a different Elasticsearch account?

Claude can manage the Elasticsearch connection for you.

  • Ask Claude to disconnect or delete the current Elasticsearch account.
  • Ask Claude to connect Elasticsearch again.
  • Open the new Composio authorization link for Elasticsearch.
  • Sign in with the other Elasticsearch account in the browser.
  • After the account connects, ask Claude to retry the Elasticsearch task.

6. Why is my Elasticsearch connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Elasticsearch connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Elasticsearch tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Elasticsearch.
TOOLS

Supported Tools

Every Elasticsearch action and event your agent gets out of the box.

Get Index Schema

Tool to get the complete schema/mapping of a specific Elasticsearch index.

List Indices

Tool to list all available Elasticsearch indices.

Ping Cluster

Tool to ping the Elasticsearch cluster and check if it is running.

Query Index

Tool to query an Elasticsearch index with various filters, time ranges, and pagination support.

FRAMEWORKS

How to build Elasticsearch MCP Agent with another framework

Claude Code logo

Claude Code

Use Elasticsearch MCP with Claude Code

Cursor logo

Cursor

Use Elasticsearch MCP with Cursor

ChatGPT logo

ChatGPT

Use Elasticsearch MCP with ChatGPT

Antigravity logo

Antigravity

Use Elasticsearch MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Elasticsearch MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Elasticsearch MCP with Claude Agent SDK

Codex logo

Codex

Use Elasticsearch MCP with Codex

Grok Build logo

Grok Build

Use Elasticsearch MCP with Grok Build

VS Code logo

VS Code

Use Elasticsearch MCP with VS Code

OpenCode logo

OpenCode

Use Elasticsearch MCP with OpenCode

OpenClaw logo

OpenClaw

Use Elasticsearch MCP with OpenClaw

Hermes logo

Hermes

Use Elasticsearch MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Elasticsearch MCP with Atomic Agent

Google ADK logo

Google ADK

Use Elasticsearch MCP with Google ADK

LangChain logo

LangChain

Use Elasticsearch MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Elasticsearch MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Elasticsearch MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Elasticsearch MCP with LlamaIndex

CrewAI logo

CrewAI

Use Elasticsearch MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Elasticsearch MCP with Pydantic AI

AutoGen logo

AutoGen

Use Elasticsearch MCP with AutoGen

FAQ

Frequently asked questions

With a standalone Elasticsearch MCP server, the agents and LLMs can only access a fixed set of Elasticsearch tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Elasticsearch and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Elasticsearch tools.

Yes, absolutely. You can configure which Elasticsearch scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Elasticsearch data and credentials are handled as safely as possible.

Start with Elasticsearch.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Elasticsearch tool your agent needs.Free to start.

Start building