Bring Virtual Receptionist
to CrewAI
Learn how to connect Goodcall to CrewAI and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Goodcall MCP Server?
Connect your Goodcall account to any AI agent and manage your virtual phone agent fleet through natural conversation.
What you can do
- Agent Management — List all virtual phone agents, inspect individual configurations, and update greeting scripts or behavior settings
- Call History — Browse all calls handled by AI agents, filter by specific agent, and inspect individual call details
- Transcripts & Summaries — Retrieve full conversation transcripts and AI-generated call summaries with key topics and outcomes
- Missed Call Tracking — Identify calls that were missed or abandoned for follow-up prioritization
- Booking Management — View all appointments booked by the AI agent during customer calls
- FAQ Configuration — List all FAQ entries configured for each agent to verify knowledge coverage
- Performance Analytics — Track aggregate metrics including total calls, answer rate, booking conversion, and trends
How it works
1. Subscribe to this server
2. Enter your Goodcall API Key from your account settings
3. Start managing your phone agents from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Small Business Owners — monitor how the AI receptionist handles calls, check bookings, and follow up on missed calls
- Operations Managers — analyze call volume, answer rates, and booking conversions across all phone agents
- Customer Service Leaders — review call transcripts, refine agent scripts, and ensure FAQ coverage
Built-in capabilities (13)
Verify connectivity
Get agent details
Get call analytics
Get call details
Get call summary
Get call transcript
List AI agents
List bookings
List all calls
List calls by agent
List FAQs
List missed calls
Update an agent
Why CrewAI?
When paired with CrewAI, Goodcall becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Goodcall 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
Goodcall in CrewAI
Goodcall and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Goodcall 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 Goodcall in CrewAI
The Goodcall 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 13 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
Goodcall for CrewAI
Every tool call from CrewAI to the Goodcall MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I review what my AI phone agent said during a customer call?
Yes. Use get_transcript with a Call ID to retrieve the full conversation transcript between the AI agent and the caller. For a quick overview, use get_call_summary which provides an AI-generated summary with key topics discussed and the call outcome (e.g., booking made, question answered, callback requested).
Can I track missed calls and see which ones need follow-up?
Yes. The list_missed_calls tool retrieves all calls that were missed or abandoned, including caller phone number, timestamp, and any partial interaction data. This helps you prioritize follow-up callbacks and identify peak call times when your agents may be overloaded.
Can I see appointments booked by the AI agent during calls?
Yes. The list_bookings tool retrieves all appointments booked by the AI agent during customer calls, including date, time, caller details, and the associated call ID. Use get_analytics to track your booking conversion rate — the percentage of calls that result in a scheduled appointment.
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.