Bring Appointment Booking
to Claude Desktop
Learn how to connect meetergo to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect meetergo to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 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
meetergo in Claude Desktop
meetergo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect meetergo 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 meetergo in Claude Desktop
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 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
meetergo for Claude Desktop
Every tool call from Claude Desktop 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.
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.