Bring Enterprise Search
to CrewAI
Create your Vinkius account to connect Elastic Enterprise Search to CrewAI and start using all 6 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
Compatible with every major AI agent and IDE
What is the Elastic Enterprise Search MCP Server?
Connect your Elastic Enterprise Search deployment to any AI agent and take full control of your application search engines and workplace discovery through natural conversation.
What you can do
- Engine Orchestration — Iterate through explicit engine containers managing logical indexing schemas and search spaces completely
- Search & Discovery — Resolve semantic or literal queries enforcing deep contextual matches against structured enterprise scopes seamlessly
- Document Indexing — Command explicit bulk payload ingestions triggering native pipeline mappings to store and update document collections synchronously
- Metadata Inspection — Analyze specific global bounds fetching discrete index layouts and extracting linguistic configuration nodes cleanly
- Analytics Auditing — Generate precise internal metric tracking isolating usage insights and calculating exact click log data to monitor performance
- Catalog Retrieval — Extract explicitly attached REST arrays mapping exact document payloads fetching physical raw records flawlessly
How it works
- Subscribe to this server
- Enter your Elastic Enterprise Search URL and API Key (found in Kibana > Stack Management > Security > API Keys)
- Start managing your search engines from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Search Engineers — monitor engine configurations and test search relevance without manual API testing
- Software Developers — index documents and verify search results directly from the IDE or chat
- Data Analysts — audit search analytics and monitor click logs using natural language conversation
- Ops Teams — verify engine health and manage document indexing pipelines in real-time
Built-in capabilities (6)
Get search analytics
Get engine
Index newly created JSON documents targeting specific schemas
List indexed documents in an engine
List engines
Search documents within an engine
Why CrewAI?
When paired with CrewAI, Elastic Enterprise Search becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Elastic Enterprise Search tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Elastic Enterprise Search in CrewAI
Why run Elastic Enterprise Search with Vinkius?
The Elastic Enterprise Search connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 6 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.




Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Elastic Enterprise Search using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Elastic Enterprise Search and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Elastic Enterprise Search to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Elastic Enterprise Search for CrewAI
Every request between CrewAI and Elastic Enterprise Search is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
Can my agent list all available search engines in Elastic?
Yes. Use the 'list_engines' tool. 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' tool. 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' tool 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.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
WCAG.com Accessibility
4 toolsAudit web accessibility — check compliance and guidelines via AI.

Gusto
10 toolsManage employees, run payroll, view benefits and time-off policies — HR automation for AI agents.

Fellow
12 toolsManage meeting notes and feedback via Fellow — list agenda items and decisions, track action items, handle recordings, and complete tasks directly from any AI agent.

Odoo Manufacturing
7 toolsCreate manufacturing orders, manage BOMs, work orders, and work centers — Odoo MRP through natural conversation.
