Bring Calendar Integration
to CrewAI
Learn how to connect Truto Unified Calendar to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Truto Unified Calendar MCP Server?
Deploy the ultimate scheduling machine by linking your AI agent to Truto. Instead of building fragmented code for individual calendar APIs, Truto provides a normalized schema that controls Google Calendar, Outlook, and countless others underneath. Command your agent to list daily events, find free timeslots accurately, or write absolute meetings directly to the chosen provider without swapping logic loops.
What you can do
- Unified Calendar Tracking — Check all connected calendars regardless of provider natively and list their available events continuously
- Meeting Generation — Instruct your AI to generate or directly cancel/update specific events passing ISO-compliant timings directly to the root provider
- Free/Busy Analysis — Demand explicit gaps inside your schedule bypassing complex metadata just extracting readable unavailable/available blocks
- Integration Audit — Check the absolute status of all connected root provider connections (Integrations) to ensure nothing is decoupled abruptly
- Event Forensics — Interrogate and extract any granular metadata embedded inside an
event_id, including conferencing details and attendee lists
How it works
- Anchor this multi-calendar instance to your local Vinkius conversational agent
- Provide the Master Token from Truto combined specifically with your
Integrated Account IDtargeting a specific linked provider - Engage scheduling queries organically conversing with your assistant
Who is this for?
- Executive Assistants — Book multi-provider meetings strictly through conversational commands checking calendar gaps dynamically
- Sales Coordinators — Force event creation securely across varied client infrastructures without logging into fragmented Google and Microsoft portals
- Platform Architects — Centralize routing logic manipulating the agent to alter calendar entries strictly using one unified schema rule
Built-in capabilities (10)
Provide calendar_id, title, and start/end times in ISO format. Create a new event in a calendar via Truto. The event is written through to the underlying provider (Google/Outlook) in real-time. Provide calendar ID, title, and ISO 8601 start/end times
This action is irreversible. Delete an event via Truto. The event is removed from both Truto and the underlying provider in real-time
Get details of a specific calendar via Truto by ID. Returns calendar name, provider, timezone, and metadata normalized to the Truto unified schema
Get full details of a specific event via Truto. Returns title, description, start/end times, attendees, location, organizer, recurrence, and provider-specific metadata
Provide calendar_id and time range. Get free/busy data for a calendar via Truto within a date range. Returns time blocks as free or busy in the unified Truto format
List all calendars via Truto unified API. Truto provides a real-time, pass-through API that normalizes calendar data across Google Calendar, Outlook Calendar, and other providers into a consistent schema
List all integrated accounts (connections) in Truto. Shows connected calendar providers, auth status, and account metadata
Provide the calendar_id. List all events from a calendar via Truto. Returns events in a unified format regardless of the underlying provider. Shows titles, times, attendees, locations, and conferencing info
Provide the event_id and a JSON updates object. Update an existing event via Truto. Provide a JSON object with fields to change. Changes pass through to the real provider in real-time
Validate a Truto integrated account connection. Checks credentials, permissions, and API accessibility. Returns validation status and any errors
Why CrewAI?
When paired with CrewAI, Truto Unified Calendar becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Truto Unified Calendar 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
Truto Unified Calendar in CrewAI
Truto Unified Calendar and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Truto Unified Calendar 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 | 4,000+ 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 Truto Unified Calendar in CrewAI
The Truto Unified Calendar 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 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
Truto Unified Calendar for CrewAI
Every tool call from CrewAI to the Truto Unified Calendar MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How and where do I collect my universal Truto API Token?
Navigate accurately toward your primary Truto management dashboard portal. Search intentionally along your workspace or developer settings focusing clearly on the API Keys section. Dictate the explicit creation of a new bearer credential. Lock the generated long string into your clipboard and transport it perfectly to the waiting field array below.
What is the Truto Integrated Account ID and where is it?
Because Truto is unified, one single environment connects entirely to many different client calendars (e.g., your Google, a client's Outlook). The Integrated Account ID designates explicitly WHICH underlying calendar provider the agent should orchestrate right now. You fetch this prefix ID commonly starting with ia_ precisely from the Integrations tab listed inside your Truto dashboard.
Should I save the Truto API Token immediately?
Yes. Once you click 'Create API Token' and it gets generated, you must copy it immediately. Truto will only show the API Token once. If you close the window without securely saving it, you will have to create a new one.
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.
Explore More MCP Servers
View all →
WHO GHO
3 toolsAccess 2,200+ health indicators from 194 countries — life expectancy, disease prevalence, mortality rates, immunization coverage, and environmental health data from the World Health Organization.
GitLab
12 toolsManage projects, track issues, and oversee CI/CD pipelines via AI agents with GitLab.
Matomo
10 toolsOpen-source web analytics via Matomo — track visits, goals, and user behavior directly from any AI agent.
Heroku (PaaS)
10 toolsManage Heroku apps via AI — list apps, restart dynos, toggle maintenance mode, and audit config vars.