Bring Appointment Booking
to Cursor
Learn how to connect meetergo to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the meetergo MCP Server?
Connect your meetergo account to any AI agent and take full control of your scheduling orchestration and appointment management through natural conversation. meetergo provides a robust platform for managing team availability and customer bookings, and this integration allows you to retrieve booking metadata, monitor team schedules, and manage meeting templates directly from your chat interface.
What you can do
- Booking & Appointment Orchestration — List all scheduled meetings and retrieve detailed metadata programmatically to ensure your calendar is always synchronized.
- Availability & Schedule Intelligence — Access and monitor team member availabilities directly from the AI interface to track throughput and identify open slots.
- Template & Type Control — List and retrieve all active meeting templates (meeting types) via natural language to facilitate frictionless meeting coordination.
- User & Context Oversight — Access granular details for specific users and their configured settings using simple AI commands to maintain a clear overview of your digital infrastructure.
- Operational Monitoring — Track system responses and manage booking metadata to ensure your scheduling pipelines are always optimized.
How it works
1. Subscribe to this server
2. Enter your meetergo API Key (starts with ak_live:) and User ID from your dashboard settings
3. Start managing your scheduling from Claude, Cursor, or any MCP-compatible client
No more manual status checking in the dashboard for new bookings. Your AI acts as a dedicated scheduling coordinator or office assistant.
Who is this for?
- Client-facing Teams — quickly retrieve booking summaries and coordinate meetings without switching apps.
- Operations Managers — automate the retrieval of team availability and track appointment loads via natural conversation.
- Developers — integrate real-time scheduling data and booking intelligence directly within the chat.
Built-in capabilities (12)
Cancel a booking
Verify connectivity
Create a booking
Get user availability
Get booking details
Get my profile
Get meeting type
Get user details
List availability
List bookings
List meeting types
List users
Why Cursor?
Cursor's Agent mode turns meetergo into an in-editor superpower. Ask Cursor to generate code using live data from meetergo and it fetches, processes, and writes. all in a single agentic loop. 12 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
meetergo in Cursor
meetergo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect meetergo 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 meetergo in Cursor
The meetergo 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 12 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
meetergo for Cursor
Every tool call from Cursor to the meetergo MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the details for a specific booking by its ID?
Yes! Use the list_bookings tool. Your agent will respond with complete metadata for the appointments, including participant info and scheduled time in seconds.
How do I find my meetergo API Key?
Log in to your meetergo account, navigate to Settings > API Keys, and you will find your unique secret token (starts with ak_live:) there.
Do I need the User ID?
Yes, many endpoints require the x-meetergo-api-user-id header. You can find your User ID in the profile settings or use the get_me tool to retrieve it via the AI.
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.