Bring Aireceptionist
to Cursor
Learn how to connect AI Receptionist to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the AI Receptionist MCP Server?
Connect your AI Receptionist account to any AI agent and take full control of your automated customer engagement and front-desk workflows through natural conversation.
What you can do
- Conversation Orchestration — List and monitor inbound and outbound AI voice or chat interactions programmatically, retrieving complete high-fidelity transcripts and operational metadata in real-time
- Booking & Appointment Intelligence — Access your complete directory of active appointments and programmatically create or manage bookings to maintain a perfectly coordinated schedule
- Knowledge Base Discovery — Access and monitor your organizational business rules and FAQs (Knowledge Base) to coordinate how your AI receptionist interacts with clients
- Lead & Performance Intelligence — Retrieve high-fidelity analytics on lead capture and interaction performance directly through your agent for instant operational reporting
- Infrastructure Monitoring — Verify API connectivity, access account metadata, and monitor active webhooks to maintain a perfectly coordinated communication ecosystem
How it works
1. Subscribe to this server
2. Retrieve your API Key from your AI Receptionist dashboard (Developer Settings > API)
3. Start orchestrating your automated front-desk from Claude, Cursor, or any MCP client
No more manual listening to call recordings or digging through individual lead tables. Your AI acts as your dedicated front-desk coordinator and interaction architect.
Who is this for?
- Business Owners — instantly retrieve lead summaries and monitor AI performance using natural language commands
- Operations Managers — manage appointment schedules and verify knowledge base accuracy without leaving your workspace
- Developers — integrate high-speed AI voice intelligence and booking data into custom business workflows through simple AI queries
Built-in capabilities (10)
Create a booking
Create a new conversation
Get performance analytics
Get booking details
Get conversation details
Get current user profile
List active bookings
List AI conversations
List knowledge base articles
List active webhooks
Why Cursor?
Cursor's Agent mode turns AI Receptionist into an in-editor superpower. Ask Cursor to generate code using live data from AI Receptionist and it fetches, processes, and writes. all in a single agentic loop. 10 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
AI Receptionist in Cursor
AI Receptionist and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect AI Receptionist 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 AI Receptionist in Cursor
The AI Receptionist 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 10 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
AI Receptionist for Cursor
Every tool call from Cursor to the AI Receptionist 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 AI Receptionist API Key?
Log in to your account, navigate to Developer Settings > API, and generate or copy your unique API Key.
Can I read call transcripts via AI?
Yes! The get_aireceptionist_conversation tool allows your agent to retrieve complete high-fidelity transcripts of any AI interaction programmatically.
How do I check lead analytics?
Use the get_aireceptionist_analytics tool to retrieve a high-fidelity summary of lead capture metrics and performance data directly through your agent.
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.