Compatible with every major AI agent and IDE
What is the The Botforge MCP Server?
Connect your The Botforge account to any AI agent and simplify how you manage your conversational AI, handle contact submissions, and monitor bot health through natural conversation.
What you can do
- Bot Oversight — List all chatbots in your account and retrieve real-time operational status for specific bot IDs.
- Contact Submission — Programmatically submit data to your bot's contact forms, ideal for automated lead capture.
- Event Integration — Subscribe to bot events via webhooks to receive real-time updates on user interactions.
- Metadata Inspection — Retrieve sample data and form field configurations to understand your bot's data structure.
- Operational Monitoring — Check connectivity and verify if your bots are online and responsive via AI queries.
How it works
- Subscribe to this server
- Enter your The Botforge API Key (found in your account dashboard)
- Start managing your conversational ecosystem from Claude, Cursor, or any MCP client
Who is this for?
- Chatbot Developers — quickly check bot statuses and test form submissions via simple AI commands.
- Marketing Teams — automate lead capture from external sources directly into your bot engine.
- Support Managers — monitor bot health and receive real-time interaction events without leaving the workspace.
Built-in capabilities (5)
Check bot operational status
Get bot form field samples
List all chatbots
Pass data as a JSON string. Submit data to the bot contact form
Pass data as a JSON string. Subscribe to bot events via webhook
Why CrewAI?
When paired with CrewAI, The Botforge becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call The Botforge 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
The Botforge in CrewAI
The Botforge and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect The Botforge 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 | 4,000+ 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 The Botforge in CrewAI
The The Botforge 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 5 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
The Botforge for CrewAI
Every tool call from CrewAI to the The Botforge MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check if a specific chatbot is online via AI?
Yes! Use the get_bot_status tool and provide the Bot ID. Your agent will retrieve the current operational state of that specific bot.
How do I submit data to my bot's contact form using the agent?
Use the submit_contact action. Provide the contact details (name, email, message) in a JSON string. The agent will transmit this data directly to the bot engine.
Is it possible to see which fields my bot expects in its form?
Absolutely. Use the get_samples query. The agent will retrieve sample data based on your bot's configured form fields, helping you understand the required structure.
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 →
Cal.com
12 toolsLet anyone book time with you through customizable scheduling pages that sync with your calendar and eliminate back-and-forth.

QRCodeChimp
11 toolsGenerate branded QR codes with tracking, analytics, and dynamic content that update without reprinting for any use case.

Dropbox Sign
12 toolsGet documents signed electronically with legally binding e-signatures, templates, and audit trails your business can trust.

Upstash Redis
7 toolsEquip your AI to directly query, manage, and manipulate key-value data structures inside your serverless Upstash Redis databases.
