Bring Virtual Receptionist
to Claude Desktop
Learn how to connect Goodcall to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect Goodcall to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 13 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Goodcall in Claude Desktop
Goodcall and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Goodcall to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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 Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.