Bring Appointment Booking
to CrewAI
Learn how to connect meetergo to CrewAI 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 CrewAI?
When paired with CrewAI, meetergo becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call meetergo tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
meetergo in CrewAI
meetergo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect meetergo to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.