Bring Voice Ai
to CrewAI
Learn how to connect Thoughtly 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 Thoughtly MCP Server?
Connect your Thoughtly voice AI platform to any text-based AI agent to seamlessly bridge the gap between text commands and real-world phone calls.
What you can do
- Trigger Phone Calls — Instantly instruct your AI Voice Agents (Interviews) to dial any contact and execute conversational phone workflows
- Contact Management — Query your Thoughtly CRM directory, register new leads with phone numbers, and manage their details
- Call Logs & Transcripts — Retrieve detailed call histories, metadata, and full transcripts of conversations conducted by your voice agents
- Agent Fleet Control — List and inspect all your active AI Voice Agents to deploy the right persona for each outbound campaign
How it works
1. Subscribe to this server
2. Enter your Thoughtly API Token and Team ID
3. Start commanding your voice agents directly from Claude, Cursor, or any MCP-compatible client
Your text agent becomes the ultimate dispatcher, effortlessly ordering your voice agents to interact with the real world through natural language.
Who is this for?
- Sales Development Reps — automate outbound qualification campaigns by triggering voice agents for new leads instantly
- Customer Support Teams — quickly query the transcript of past AI interactions without opening a dashboard
- Operations Managers — orchestrate complex communication workflows across both text and voice channels simultaneously
Built-in capabilities (11)
Optionally includes first name, last name, email. Create a new Thoughtly contact
Delete a Thoughtly contact
Get details and transcript for a specific call
Get specific Thoughtly contact details
Get details for a specific Thoughtly Voice Agent
Get Thoughtly user details
List past phone calls (Call logs)
List Thoughtly contacts
List Thoughtly Voice Agents (Interviews)
Trigger an AI outbound phone call
Update an existing Thoughtly contact
Why CrewAI?
When paired with CrewAI, Thoughtly becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Thoughtly 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
Thoughtly in CrewAI
Thoughtly and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Thoughtly 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 Thoughtly in CrewAI
The Thoughtly 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
Thoughtly for CrewAI
Every tool call from CrewAI to the Thoughtly MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my text AI agent command a voice agent to call a specific person?
Yes! Use the trigger_call tool by providing the Interview ID (Voice Agent) and the Contact ID. The voice AI will immediately execute the outbound call.
Is it possible to read the transcript of what the Voice AI discussed during a call?
Absolutely. By calling the get_call_history tool with a specific Call ID, your agent can extract the entire conversational transcript and analyze the outcome without leaving the interface.
Do I need to manually register contacts in the Thoughtly dashboard before calling them?
No. The integration provides the create_contact tool, allowing your AI to dynamically add new leads to the CRM and immediately initiate a phone call in one fluid workflow.
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.