Bring Chatbot Training
to CrewAI
Learn how to connect Botsonic to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Botsonic MCP Server?
Connect your Botsonic (by Writesonic) account to any AI agent and manage your AI chatbot fleet through natural conversation.
What you can do
- Bot Management — Create, update, list, and inspect AI chatbots with personality, instructions, and knowledge base configuration
- Knowledge Base Training — Add web page URLs to a bot's knowledge base and review all training sources (URLs, documents, files)
- Conversation History — Browse all chat sessions per bot and inspect the full message history of any conversation
- Live Querying — Send messages to a bot and receive AI-generated responses in real time
- Lead Capture — Retrieve all leads collected by the chatbot during customer conversations
- Performance Analytics — Track usage metrics including conversation volume, message count, resolution rate, and customer satisfaction
How it works
1. Subscribe to this server
2. Enter your Botsonic API Token from your Writesonic dashboard
3. Start managing your chatbot fleet from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Customer Support Teams — monitor bot conversations, review resolution rates, and capture leads without switching dashboards
- Product Managers — train bots with new knowledge sources and test responses through conversational AI
- Growth Teams — analyze chatbot engagement metrics and lead capture performance across all bots
Built-in capabilities (12)
Add knowledge URL
Verify connectivity
Create a bot
Get bot details
Get bot analytics
Get conversation
List all bots
List conversations
List knowledge base
List captured leads
Send message to bot
Update a bot
Why CrewAI?
When paired with CrewAI, Botsonic becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Botsonic 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
Botsonic in CrewAI
Botsonic and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Botsonic 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 Botsonic in CrewAI
The Botsonic 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 12 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
Botsonic for CrewAI
Every tool call from CrewAI to the Botsonic MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I train a bot by adding web pages to its knowledge base?
Yes! The add_knowledge_url action accepts a Bot ID and a URL. Botsonic will crawl the page and add its content to the bot's training data. Use list_knowledge_base to review all sources (URLs, documents, files) currently training a specific bot.
Can I retrieve leads captured by my chatbot during customer interactions?
Yes. The list_leads tool retrieves all leads collected by a specific bot during conversations, including contact details, conversation context, and capture timestamp. This is ideal for syncing chatbot-qualified leads into your CRM.
How can I measure the performance of my chatbots?
Use get_bot_analytics with the Bot ID. It returns conversation count, total messages, resolution rate (percentage of conversations resolved without human handoff), and customer satisfaction scores. Compare across bots to identify which ones need KB improvements.
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.