Bring Virtual Receptionist
to Cursor
Learn how to connect Goodcall to Cursor 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 Cursor?
Cursor's Agent mode turns Goodcall into an in-editor superpower. Ask Cursor to generate code using live data from Goodcall and it fetches, processes, and writes. all in a single agentic loop. 13 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Goodcall in Cursor
Goodcall and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Goodcall to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.