Bring Vector Database
to CrewAI
Create your Vinkius account to connect OpenSearch Vector 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 OpenSearch Vector MCP Server?
Turn your OpenSearch cluster into an AI-native vector database. Create k-NN indexes, upsert embeddings, run similarity searches, and inspect index configurations — all through natural conversation with your AI agent.
What you can do
- Vector Search — Execute k-Nearest Neighbors queries against any k-NN index with custom top-K limits and dense float vectors
- Index Management — List all cluster indexes with health status and document counts, or inspect a specific index's vector dimension, engine config, and distance metric
- Create Index — Provision new k-NN indexes optimized for cosine similarity with configurable vector dimensions (384, 768, 1536, etc.)
- Document Operations — Upsert vector documents with metadata, or delete documents from the embedding space by ID
How it works
- Subscribe to this server
- Enter your OpenSearch Host, Username, and Password
- Start managing your vector store from Claude, Cursor, or any MCP-compatible client
Who is this for?
- ML engineers — test similarity queries against production embeddings without writing curl commands
- RAG developers — index and retrieve context documents for retrieval-augmented generation pipelines
- Data teams — inspect index health, document counts, and vector configurations through conversation instead of Kibana dashboards
Built-in capabilities (6)
knn: true` and mapping a rigid dynamic dense vector field optimized for cosine similarity. Create a new native OpenSearch KNN index ready for vector embeddings
Delete an explicit vector document bounding from OpenSearch
Retrieve explicit OpenSearch index mapping and settings
This executes a fast transactional atomic insertion into the embedding space. Upsert a singular vector document directly into an OpenSearch KNN index
List all explicit indexes residing on the OpenSearch cluster
Provide the exact index name and a JSON-stringified dense float vector array to find conceptually similar embeddings natively. Execute a K-Nearest Neighbors (k-NN) vector search against OpenSearch
Why CrewAI?
When paired with CrewAI, OpenSearch Vector becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call OpenSearch Vector 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
OpenSearch Vector in CrewAI
Why run OpenSearch Vector with Vinkius?
The OpenSearch Vector 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 OpenSearch Vector using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
OpenSearch Vector and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect OpenSearch Vector 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
OpenSearch Vector for CrewAI
Every request between CrewAI and OpenSearch Vector 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
What vector dimensions does it support?
Any dimension supported by OpenSearch k-NN. Common values: 384 (MiniLM), 768 (BERT/all-mpnet), 1536 (OpenAI text-embedding-ada-002), 3072 (text-embedding-3-large). When creating an index, specify the exact dimension and the agent provisions the mapping automatically.
Can I delete an entire index or just individual documents?
Currently, the agent supports deleting individual documents by ID from an index. Full index deletion is not exposed through this integration to prevent accidental data loss. If you need to drop an index, use the OpenSearch Dashboards or direct API calls.
Does this work with Amazon OpenSearch Service (managed)?
Yes. Provide the Amazon OpenSearch Service endpoint as the host (e.g., https://search-xxx.us-east-1.es.amazonaws.com) along with the master username and password. The integration uses standard REST APIs that work identically on managed and self-hosted clusters.
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 →
Tencent Cloud VOD / 腾讯云点播
8 toolsTencent's dominant video-on-demand platform — manage media, track tasks, and audit storage via AI.

Bing Search
8 toolsEmpower your AI agent with real-time web, image, and news search via Bing.

ProTexting
12 toolsAutomate SMS marketing via ProTexting — manage campaigns, contacts, and keywords directly with AI.

Have I Been Pwned
5 toolsCheck if your accounts or passwords have been compromised in data breaches using the HIBP service.
