How do I connect my Elastic deployment?

You need your Elastic Enterprise Search URL and an API Key. You can find the API Key in Kibana under Stack Management, then Security, then API Keys.

Which AI clients can use this MCP?

This MCP works with any compatible client, including Claude, Cursor, Windsurf, and VS Code.

Can I use this to index new data?

Yes, you can use the index_documents capability to send JSON payloads to your specific engine schemas.

Is my data being stored by Vinkius?

Vinkius hosts the MCP and manages the connection, but the data remains within your Elastic deployment.

Can I check search performance through the agent?

Yes, the analytics capability allows you to pull usage insights and click log data directly through your AI client.

Can my agent list all available search engines in Elastic?

Yes. Use the 'list_engines' capability. The agent iterates through your engine containers, managing logical indexing schemas and providing a complete map of your search spaces.

How do I index a batch of JSON documents via chat?

Use the 'index_documents' capability. Provide the engine name and a JSON array of your documents. The agent will command the bulk payload ingestion, triggering native pipeline mappings to store your data synchronously.

Can I check the search analytics for a specific engine through the agent?

Absolutely. The 'analytics' capability generates precise internal metric tracking for your engine. It will isolate usage insights and calculate click log data, allowing you to monitor search performance natively.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Elastic Enterprise Search to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Run and manage your search infrastructure through natural conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 6 capabilities

We ship only the actions that matter.

Capability set01 / 02

01-03

3 capabilities in this set.

Part of 6 available through Elastic Enterprise Search.

01
Index documents
This capability sends JSON documents to your specified engine schemas for indexing.
02
List documents
Use this to see all the documents currently stored within a specific engine.
03
Search
This capability runs queries against an engine to find matching documents.

Capability set02 / 02

04-06

3 capabilities in this set.

Part of 6 available through Elastic Enterprise Search.

04
Analytics
Get search performance metrics and usage insights directly from your engine.
05
Get engine
This capability retrieves the specific configuration and details for a single engine.
06
List engines
Use this to see a full list of all engines in your Elastic deployment.

Real work

What teams actually run

Rapid Prototyping

Index new JSON documents and immediately test search queries to verify schema accuracy.

Search Performance Monitoring

Ask your agent for recent click logs to see how users are interacting with your search results.

Engine Auditing

Quickly pull engine configurations to ensure they match your intended deployment specs.

Data Discovery

Retrieve specific document payloads and metadata to verify the contents of your index.

Automate a task

Put Elastic Enterprise Search to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Elastic Enterprise Search works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Elastic Enterprise Search to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

838ms average. Fast in production.

Elastic Enterprise Search is checked daily against the live service.

Daily averagePeak 988ms

Oct 3Today

Fastest day: 735ms
Slowest day: 988ms
14-day trend: Slowing+7%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 6 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Elastic Enterprise Search, so you can see the experience inside your AI.

It does not authenticate your account with Elastic Enterprise Search. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Elastic Enterprise Search Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_qKt4LErFxKdXqt4yKDgRA4vftlbXFWLYnCIqSS0l/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Elastic Enterprise Search capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

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

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Elastic Enterprise Search in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Elastic Enterprise Search owners hand off.

This MCP is built for technical teams who need to interact with Elastic without constant manual API calls.

01
Search Engineers
They use the agent to test search relevance and monitor engine configurations.
02
Software Developers
They index documents and verify search results directly from their IDE.
03
Data Analysts
They audit search analytics and click logs using natural language.
04
Ops Teams
They manage indexing pipelines and verify engine health in real-time.

FAQ

Questions Elastic Enterprise Search owners ask.

01
How do I connect my Elastic deployment?
You need your Elastic Enterprise Search URL and an API Key. You can find the API Key in Kibana under Stack Management, then Security, then API Keys.
02
Which AI clients can use this MCP?
This MCP works with any compatible client, including Claude, Cursor, Windsurf, and VS Code.
03
Can I use this to index new data?
Yes, you can use the index_documents capability to send JSON payloads to your specific engine schemas.
04
Is my data being stored by Vinkius?
Vinkius hosts the MCP and manages the connection, but the data remains within your Elastic deployment.
05
Can I check search performance through the agent?
Yes, the analytics capability allows you to pull usage insights and click log data directly through your AI client.
06
Can my agent list all available search engines in Elastic?
Yes. Use the 'list_engines' capability. The agent iterates through your engine containers, managing logical indexing schemas and providing a complete map of your search spaces.
07
How do I index a batch of JSON documents via chat?
Use the 'index_documents' capability. Provide the engine name and a JSON array of your documents. The agent will command the bulk payload ingestion, triggering native pipeline mappings to store your data synchronously.
08
Can I check the search analytics for a specific engine through the agent?
Absolutely. The 'analytics' capability generates precise internal metric tracking for your engine. It will isolate usage insights and calculate click log data, allowing you to monitor search performance natively.

Explore

More in Industry Titans

Connect Elastic Enterprise Search to Claude, Cursor, ChatGPT & more

Your AI does the work. We keep it safe and sound.

Each Connector runs inside its own sealed environment.

One switch stops every agent. Instantly.

Spending limits that pause instead of surprise.

We ship only the actions that matter.

01-03

Index documents

List documents

Search

04-06

Analytics

Get engine

List engines

What teams actually run

Rapid Prototyping

Search Performance Monitoring

Engine Auditing

Data Discovery

Building your own app? The connector is yours to use.

Elastic Enterprise Search Connector

Claude Desktop

Search Engineers

Software Developers

Data Analysts

Ops Teams

How do I connect my Elastic deployment?

Which AI clients can use this MCP?

Can I use this to index new data?

Is my data being stored by Vinkius?

Can I check search performance through the agent?

Can my agent list all available search engines in Elastic?

How do I index a batch of JSON documents via chat?

Can I check the search analytics for a specific engine through the agent?

Lucidworks Fusion (AI Search & Discovery) AI Connector

Vertex AI Search AI Connector

FRED Tags & Sources — Data Discovery AI Connector

watsonx Discovery AI Connector

Suggestions

UK ONS Discovery — Search 337+ Statistical Datasets AI Connector

Data Pipeline Prover AI Connector

Azure Cognitive Search AI Connector

Data.gov Catalog AI Connector