Bring Multi Agent Systems
to CrewAI
Create your Vinkius account to connect Relevance AI to CrewAI and start using all 10 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.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Relevance AI MCP Server?
Connect your conversational AI to your Relevance AI workspace. By wrapping your custom agents, datasets, and API tools into this MCP extension, you transform your chat interface into a command center for orchestrating complex, autonomous AI operations and large-scale data workflows.
What you can do
- Orchestrate Agents — Command your pre-built autonomous agents to execute tasks (
trigger_agent). Monitor their progress and read their exact reasoning steps dynamically (get_agent_run). Uselist_agentsto discover all available AI worker configurations. - Execute Tasks & Workflows — Trigger predefined chained prompts or specific micro-tasks without leaving your chat (
trigger_task), scaling repetitive workflows reliably. - Manage Knowledge Datasets — Take full control of your vector databases and tables. Insert new rows of knowledge directly from conversational context (
insert_documents), retrieve raw unstructured data entries (get_documents), or surgically delete obsolete knowledge base items (delete_documents).
How it works
- Add the Relevance AI extension to your MCP hub.
- Supply your
Project ID,API Key, and your assignedRegion(e.g., "us-east-1" or "v2") from your Relevance AI settings. - Prompt your assistant: "Trigger the 'Lead Research' agent with the company name 'Google' and monitor the run until completion. Then, insert the output directly into our 'competitors' dataset."
Who is this for?
- AI Engineers & Builders — Run end-to-end tests on your chained logic and customized agents directly from your terminal or chat without touching the studio GUI.
- Data Analysts — Move processed insights, raw texts, and structured metadata into Relevance AI datasets using natural language.
- Operations Teams — Combine the output of your everyday AI chat intimately with your specialized Relevance AI autonomous agents for highly productive compounding workflows.
Built-in capabilities (10)
This action is irreversible. Deletes documents from a dataset by their IDs
Retrieves the status and logs of a specific agent run
Retrieves documents from a dataset
Provide documents as a JSON array of objects. Inserts documents into a dataset
Lists all AI agents in the Relevance AI studio
Lists all datasets (knowledge tables) in the project
Lists all tasks (chained prompts) in the studio
Lists all custom tools registered in the studio
Provide inputs as a JSON object. Triggers an AI agent execution
Triggers a specific task execution
Why CrewAI?
When paired with CrewAI, Relevance AI becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Relevance AI 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
Relevance AI in CrewAI
Why run Relevance AI with Vinkius?
The Relevance AI 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 10 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 Relevance AI using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Relevance AI and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Relevance AI 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
Relevance AI for CrewAI
Every request between CrewAI and Relevance AI 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 the agent monitor a long-running relevance AI agent task?
Yes. You can trigger an agent using trigger_agent, and because it provides a run_id, you can explicitly prompt your local Assistant to periodically "check in on the status using get_agent_run every minute until finished" or ask it to summarize the step-by-step agent logs after completion.
What is the differences between tasks, tools, and agents in Relevance AI?
Agents are autonomous workers capable of making step-by-step reasoning choices based on instructions and tools. Tasks are linear, pre-chained sets of commands and prompts. Tools (list_tools) are the individual capabilities, like a custom API integration or web scraper, that tasks and agents utilize to perform their actions.
How do I find my specific Region and Project ID?
These details are typically nested within the URL string when you are logged into your workspace or found globally in your developer API keys configuration pane inside your Relevance AI team dashboard. The Region is usually something like 'us-east-1' or 'v2'.
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 →
Mambu
11 toolsManage clients, loans, deposits, and tasks on Mambu Cloud Banking Platform.
Humanitix
10 toolsManage events, tickets, and attendees via Humanitix API.
Feishu Bitable
10 toolsCollaborative multi-dimensional table platform by Lark — manage bases, tables, and records via AI.
Sprout Social
10 toolsEmpower your AI with a full social media command center. Draft posts, track global analytics, and master listening topics natively across all brands.