Elastic Enterprise Search Connector for AI agents.
6 live capabilities
Manage your corporate search engines and document indexing through natural conversation.
Waiting for input…
Why people use Elastic Enterprise Search
Elastic Enterprise Search for managing enterprise search engines
With this Connector, you just tell your agent what you need. It finds the engine, runs the search, and gives you the results in one turn. You get your answers without the tab switching fatigue.
What Vinkius changes
You get a conversational interface for managing your entire Elastic search infrastructure.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 5,900+ Connectors
- Real-world use case 01
Verifying a bulk data upload
A developer wants to make sure a new product batch hit the index.
- Real-world use case 02
Auditing search relevance
A search engineer wants to know why a specific term isn't ranking well.
- Real-world use case 03
Inspecting search schemas
A data analyst needs to see the configuration for the HR portal.
Complete set · 6capabilities
The complete Elastic Enterprise Search capability set.
These are the exact actions your AI can choose when you ask it to work with Elastic Enterprise Search.
01—03
3 capabilities in this set.
Part of 6 available through Elastic Enterprise Search.
- 01 Capability
Get engine
Pulls the specific configuration and schema for a single search engine.
- 02 Capability
Search
Runs a query against a specific engine to find documents based on your request.
- 03 Capability
List documents
Shows a list of the documents currently indexed in a specific engine.
04—06
3 capabilities in this set.
Part of 6 available through Elastic Enterprise Search.
- 04 Capability
Index documents
Sends bulk JSON payloads to be stored in your search engine.
- 05 Capability
List engines
Shows all search engines in your deployment so you can pick the right one.
- 06 Capability
Analytics
Fetches click logs and usage metrics to see how people are using your search.
Set up in minutes
One URL. Then ask Elastic Enterprise Search to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Elastic Enterprise Search from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_qKt4LErFxKdXqt4yKDgRA4vftlbXFWLYnCIqSS0l/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it Elastic Enterprise Search, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable Elastic Enterprise Search for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_qKt4LErFxKdXqt4yKDgRA4vftlbXFWLYnCIqSS0l/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Elastic Enterprise Search URL.
- Step 03
Save and start
Save the connection and enable Elastic Enterprise Search in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"elastic-enterprise-search": {
"url": "https://edge.vinkius.com/vk_preview_qKt4LErFxKdXqt4yKDgRA4vftlbXFWLYnCIqSS0l/mcp"
}
}
}- Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using Elastic Enterprise Search
Open Agent mode in chat and ask: "Using Elastic Enterprise Search, help me...". 6 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"elastic-enterprise-search": {
"url": "https://edge.vinkius.com/vk_preview_qKt4LErFxKdXqt4yKDgRA4vftlbXFWLYnCIqSS0l/mcp"
}
}
}- Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using Elastic Enterprise Search
Ask Copilot: "Using Elastic Enterprise Search, help me...". 6 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"elastic-enterprise-search": {
"url": "https://edge.vinkius.com/vk_preview_qKt4LErFxKdXqt4yKDgRA4vftlbXFWLYnCIqSS0l/mcp"
}
}
}- Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using Elastic Enterprise Search
Open Cascade and ask: "Using Elastic Enterprise Search, help me...". 6 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"elastic-enterprise-search": {
"url": "https://edge.vinkius.com/vk_preview_qKt4LErFxKdXqt4yKDgRA4vftlbXFWLYnCIqSS0l/mcp"
}
}
}- Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using Elastic Enterprise Search
Ask Cline: "Using Elastic Enterprise Search, help me...". 6 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add elastic-enterprise-search --transport http "https://edge.vinkius.com/vk_preview_qKt4LErFxKdXqt4yKDgRA4vftlbXFWLYnCIqSS0l/mcp"- Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using Elastic Enterprise Search
Ask Claude: "Using Elastic Enterprise Search, show me...". 6 tools are ready
Where the request belongs
Work Elastic Enterprise Search can move forward.
This is for search engineers tired of manual API testing, developers who want to verify data without leaving their code editor, and data analysts who need to pull usage insights without writing complex DSL.
Search Engineer
Uses the Connector to check engine configurations and test search relevance without opening extra browser tabs.
Software Developer
Verifies that new documents are successfully indexed and searchable directly from their IDE.
Data Analyst
Queries click logs and search analytics to identify high performing search terms and user trends.
Ops Team Member
Monitors engine health and verifies that document indexing pipelines are running as expected.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsMeilisearch
Manage your Meilisearch instance. handle indexes, documents, and search configurations directly from your AI agent.
Lucidworks Fusion (AI Search & Discovery)
Manage AI-powered search via Lucidworks Fusion. execute semantic queries, index documents, and monitor ML training jobs.
LlamaIndex (AI Data Framework & RAG)
Query and manage RAG pipelines via LlamaIndex. execute natural language searches, audit indexed files, and monitor data pipelines.
Glean
Search across all your company apps and docs with AI that understands your organization and surfaces the right answer instantly.
Swiftype
Connect your AI to Elastic Swiftype. Query your search engines, manage documents, and retrieve deep analytical insights natively from the terminal.
Marqo AI (Vector Search & Embeddings)
Manage semantic search via Marqo. execute tensor queries, index JSON documents, and audit vector indices.
Bring your own AI
Change the model, client or framework. Keep Elastic Enterprise Search connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about Elastic Enterprise Search.
The practical details behind the request, access and result.
Can I use Elastic Enterprise Search MCP to manage my search data?
Yes, it lets you manage search engines and documents via your AI client. You can perform actions like indexing new data or searching for records through a natural conversation.
How do I connect Elastic Enterprise Search MCP to my agent?
You just need your URL and API Key from your Kibana security settings. Once you have those, you can add them to your Connector client configuration to get started.
Can this Connector help with my search relevance?
Yes, you can use it to audit analytics and see what users are clicking on. This helps you identify which results are actually useful to your audience.
Does Elastic Enterprise Search MCP support bulk indexing?
Yes, it allows you to send JSON payloads to your search engine. This makes it easy to push large sets of data into your index in one go.
Is Elastic Enterprise Search MCP good for data analysts?
It is great for pulling click logs and usage metrics without writing code. It allows you to query your search performance using plain English.
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.
One connection away
Give your agent a direct line to Elastic Enterprise Search.
Connect Elastic Enterprise Search once. Keep it beside 5,900+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available