How to Use the Elastic Enterprise Search MCP in Claude

Q: How do I search my Elastic Enterprise Search engines using Claude Desktop?

You ask your agent to search, and it invokes the search tool with your query and engine name. The server routes the request to your Elastic instance and returns the matched documents directly in your chat.

Q: What happens if my engine schema changes while using this tool?

The getengine tool fetches the updated engine schema metadata. Your agent inspects this new schema before running indexdocuments to ensure your payload fields match the expected types.

Run search queries, index JSON documents, and monitor analytics inside Claude Desktop without leaving your chat window.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Elastic Enterprise Search MCP to Claude Desktop

Create your Vinkius account to connect Elastic Enterprise Search to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Elastic Enterprise Search with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Query your engines directly inside Claude Desktop

The `search` tool and `list_engines` tool let you query your Elastic engines and inspect their configurations directly from your Claude Desktop chat window. Your agent pulls raw search results instantly, letting you debug query relevance or check document boosting on the fly. Instead of jumping to the Kibana console, you ask your agent to run test queries. It uses the returned JSON payload to analyze why a document isn't ranking where it should, saving you from constant context switching.

Index documents on the fly with this MCP Server

The `index_documents` tool allows you to push new JSON payloads directly into your Elastic engines right from Claude Desktop. You feed the local file path or raw JSON to your agent, and it formats the payload to match your schema requirements. This MCP server runs locally via stdio, meaning your agent interacts with your local development databases to pull raw records and index them. You avoid writing throwaway python scripts just to test a new indexing pipeline.

Audit search performance and document listings

The `analytics` tool and `list_documents` tool give you immediate visibility into what your users are looking for and what is actually indexed. Your agent pulls top search terms, click-through rates, and document counts directly into Claude Desktop. You use these metrics to spot search gaps, like high-volume queries returning zero results. By analyzing this telemetry, the agent suggests schema changes or synonym sets to fix the discovery bottlenecks.

Setup guide

Set up Elastic Enterprise Search MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Elastic Enterprise Search MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Elastic Enterprise Search MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under elastic-enterprise-search-mcp.

json

{
  "mcpServers": {
    "elastic-enterprise-search-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Elastic Enterprise Search. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Elastic Enterprise Search now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Elastic Enterprise Search MCP in Claude Desktop

You ask your agent to search, and it invokes the `search` tool with your query and engine name. The server routes the request to your Elastic instance and returns the matched documents directly in your chat.

Yes, you can point your agent to a local JSON file in your Claude Desktop workspace. The agent reads the file contents and uses the `index_documents` tool to push those records into your specified engine.

It runs as a local subprocess via stdio transport. You configure it in your `claude_desktop_config.json` file with your Elastic URL and API key, allowing Claude Desktop to call the tools securely.

The `get_engine` tool fetches the updated engine schema metadata. Your agent inspects this new schema before running `index_documents` to ensure your payload fields match the expected types.

All your raw JSON documents and search queries stay local to your machine before being sent directly to your Elastic Cloud endpoint. The MCP server establishes a direct connection, meaning your indexing payloads are never stored or inspected by third parties.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript