Bring Chatbot Builder
to CrewAI
Learn how to connect Typebot to CrewAI and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Typebot MCP Server?
Connect your Typebot account to any AI agent and simplify how you build, manage, and analyze your conversational assistants through natural conversation.
What you can do
- Bot Management — List all typebots across your workspaces and folders, and retrieve detailed metadata and flow structures.
- Deployment Control — Publish the latest bot changes to production instantly without leaving your agent.
- Result Analysis — List and export user submissions and conversation results to track leads and performance.
- Organization Oversight — Manage workspaces and folders to keep your conversational projects structured.
- Session Testing — Programmatically start new chat sessions to verify bot logic and user experiences.
How it works
1. Subscribe to this server
2. Enter your Typebot API Token (found in your account settings)
3. Start managing your conversational forms from Claude, Cursor, or any MCP client
Who is this for?
- Conversation Designers — quickly verify bot logic and publish updates via simple AI commands.
- Marketing & Sales Teams — monitor incoming results and export lead data directly from the workspace.
- Product Managers — get instant bird's-eye views of bot performance and organization folders via the AI assistant.
Built-in capabilities (8)
Permanently delete a typebot
Essential for reviewing the bot logic. Get details and structure for a specific typebot
Folders are used to group related typebots. List all folders in a workspace
Essential for data analysis and lead export. List collected user responses for a bot
Can be filtered by a specific workspace ID. List all conversational typebots
Workspaces contain folders and bots. List all accessible Typebot workspaces
Requires the unique bot ID. Publish and deploy the latest bot changes
Useful for testing bot flows or automated interactions. Programmatically start a new bot conversation
Why CrewAI?
When paired with CrewAI, Typebot becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Typebot 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
Typebot in CrewAI
Typebot and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Typebot 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 Typebot in CrewAI
The Typebot 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 8 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
Typebot for CrewAI
Every tool call from CrewAI to the Typebot MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I publish a bot after making changes via AI?
Yes! Use the publish_typebot action and provide the unique bot ID. Your agent will instantly deploy the latest changes to the public URL.
How do I see the submissions or leads collected by a bot?
Run the list_typebot_results query with your Typebot ID. The agent will retrieve the complete history of user responses and collected data.
Is it possible to list bots from a specific workspace?
Absolutely. Use the list_typebots tool and provide the optional workspace_id to retrieve only the bots associated with that team area.
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.