Bring Cloud Pbx
to CrewAI
Learn how to connect Callpicker to CrewAI and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Callpicker MCP Server?
Connect your Callpicker account to any AI agent and take full control of your cloud-based business telephony and virtual PBX workflows through natural conversation.
What you can do
- Call Orchestration — Programmatically initiate high-fidelity phone calls from your virtual PBX numbers to any destination worldwide directly through your agent
- Communication Intelligence — Monitor real-time incoming and outgoing call history and retrieve detailed logs and high-fidelity Call Detail Records (CDR)
- Recording Management — Access and retrieve secure download URLs for call recordings to maintain high-fidelity oversight of customer interactions
- PBX & Extension Architecture — Access your complete directory of virtual phone numbers and PBX extensions to coordinate your internal communication structure
- Operational Monitoring — Check real-time system status and generate performance reports over specific date ranges directly through your agent
How it works
1. Subscribe to this server
2. Retrieve your Client ID and Client Secret from the Callpicker Portal (Configuration > API)
3. Start managing your business voice pipeline from Claude, Cursor, or any MCP client
No more manual logging of phone results or digging through complex PBX portals. Your AI acts as your dedicated telephony engineer and voice coordinator.
Who is this for?
- Sales & Support Teams — instantly initiate calls to leads and retrieve conversation recordings using natural language commands
- Operations Managers — monitor PBX system health and automate call log analysis without leaving your workspace
- Developers — integrate high-speed virtual calling and CDR data into custom workflows through simple AI queries
Built-in capabilities (9)
Get details for a specific call
Get Call Detail Records (CDR)
Check PBX system status
Get the download URL for a recording
List recent call logs
List available call recordings
List PBX extensions
List virtual phone numbers
Initiate a phone call
Why CrewAI?
When paired with CrewAI, Callpicker becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Callpicker 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
Callpicker in CrewAI
Callpicker and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Callpicker 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 Callpicker in CrewAI
The Callpicker 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 9 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
Callpicker for CrewAI
Every tool call from CrewAI to the Callpicker 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 Callpicker Client ID and Secret?
Log in to the Callpicker Portal, navigate to Configuration > API, and generate your credentials.
Can I retrieve call recordings via AI?
Yes! The get_recording_url tool provides a temporary secure link to play or download any recorded interaction in your account.
How do I check my virtual numbers?
Use the list_virtual_numbers tool to retrieve your complete directory of active virtual phone numbers programmatically.
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.