Bring Aidbase
to CrewAI
Learn how to connect Aidbase to CrewAI and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Aidbase MCP Server?
Connect your Aidbase account to any AI agent and take full control of your automated customer support and intelligent knowledge management workflows through natural conversation.
What you can do
- Chatbot Orchestration — List and manage all configured AI chatbots programmatically, retrieving detailed high-fidelity metadata and configuration settings in real-time
- Knowledge Graph Ingestion — Programmatically update what your AI knows by pushing new website URLs or injecting specific Q&A items into existing FAQs dynamically
- Conversational Intelligence — Send messages and retrieve high-fidelity AI responses from specific chatbots to test performance or integrate chat into custom workflows
- AI Email Inbox Management — Access and monitor your automated email responders and their assigned knowledge bases to ensure perfectly coordinated context application
- Operational Monitoring — Verify API connectivity and retrieve account-level status directly through your agent for instant performance reporting
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Aidbase dashboard (Settings > API Keys)
3. Start orchestrating your customer service intelligence from Claude, Cursor, or any MCP client
No more manual logging into support portals to update FAQs or check bot logs. Your AI acts as your dedicated support engineer and knowledge architect.
Who is this for?
- Customer Support Leads — instantly update AI knowledge bases with fresh documentation using natural language commands
- Product Managers — monitor chatbot interactions and verify responder accuracy without leaving your workspace
- Developers — integrate high-speed AI support intelligence into custom internal tools through simple AI queries
Built-in capabilities (11)
Add FAQ to knowledge base
Add a website to knowledge base
Check API Status
Get Chatbot details
Get AI Inbox details
List Chatbot knowledge items
List all AI Chatbots
List Inbox knowledge items
List Email AI Inboxes
List all Knowledge items
Send a message to a Chatbot
Why CrewAI?
When paired with CrewAI, Aidbase becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Aidbase 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
Aidbase in CrewAI
Aidbase and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Aidbase to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Aidbase in CrewAI
The Aidbase MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Aidbase for CrewAI
Every tool call from CrewAI to the Aidbase MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Aidbase API Key?
Log in to your account, navigate to Settings > API Keys, and generate a new key for your integration.
Can I test bot responses via AI?
Yes! The send_aidbase_reply tool allows your agent to interact with specific bots and retrieve high-fidelity AI responses programmatically.
How do I teach the AI a new URL?
Use the add_aidbase_website_knowledge tool and provide the target URL. Aidbase will automatically crawl and index the content for your bots.
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.