Truto Unified Calendar MCP. Manage your schedule across every calendar in one place.
The Truto Unified Calendar MCP lets your agent handle scheduling across any calendar provider—Google, Outlook, and more. Instead of juggling multiple logins or writing complex code for different APIs, you treat all connected accounts as one unified system. Your AI client reads availability, creates meetings, and updates events in real-time across every linked service.
Claude 
ChatGPT 
Cursor 
Gemini 
Windsurf 
VS Code 
JetBrains 
Vercel Give Claude and any AI agent real-world access
It scans multiple connected calendars to find blocks of time when everyone is free.
Your agent writes new events or changes details, passing the updates directly to the root calendar provider.
It retrieves a list of every linked calendar account and its current connection status.
You can ask for full information on any single meeting, including attendee lists or conferencing links.
It checks if all linked accounts are still active and have the necessary permissions to function.
Ask an AI about this
Waiting for input…
What AI agents can do with Truto Unified Calendar: 10 Available Tools
Use these tools to perform every scheduling action possible: check availability, write new events, modify existing ones, and manage all connected accounts.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Truto Unified Calendar MCPCreate Event
Writes a new event to any linked calendar by providing the ID, title, and start/end times in ISO format.
Delete Event
Removes an existing meeting from both Truto and the underlying provider; this action...
Get Calendar
Retrieves specific details about a single calendar, including its name, timezone...
Get Event
Gets the full details of a specific meeting, returning information like attendees...
Get Free Busy
Checks availability within a date range for a calendar by returning time blocks...
List Calendars
Retrieves all connected calendars, unifying the data from services like Google and Outlook into one consistent list.
List Connections
Shows a comprehensive list of all integrated accounts and their current authentication status across providers.
List Events
Lists every event associated with a calendar ID, showing titles, times, locations...
Update Event
Modifies an existing meeting by passing a specific JSON object containing the fields...
Validate Connection
Verifies credentials and permissions for a connected account, reporting any errors...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Truto Unified Calendar integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Truto Unified Calendar, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Truto. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Pain of Calendar Fragmentation
Right now, booking a simple cross-department meeting is a multi-step headache. You have to log into Google, manually compare time slots; then switch over to Outlook and do the same thing for the other attendees. If you use an old script, you'll find yourself writing conditional logic just to handle whether the event needs to go through Microsoft or Google.
With this MCP connected via Vinkius, your agent handles the whole sequence in one conversational turn. You ask it what time works, and it checks every linked calendar simultaneously, giving you a single, actionable result instead of three different screens.
Truto Unified Calendar MCP Gives You True Scheduling Power
You no longer have to write custom logic loops or maintain separate API calls for every platform. Instead, you simply tell your agent to perform the action—be it `create_event` or checking availability using `get_free_busy`.
The system now treats all of your calendars as one unified data layer. It's a massive improvement over what was possible just months ago.
What Truto Unified Calendar MCP does for your AI
Managing a schedule today means dealing with fragmented tools. You're constantly switching between Google Calendar, Outlook, and whatever else your company uses just to see if two people are free at the same time. This MCP solves that by giving your AI agent access through one unified API layer. It reads all connected calendars—regardless of which provider owns them—and presents a single source of truth for your availability.
You can tell your assistant, 'Book a meeting with Jane and Mark next Tuesday,' and it handles checking gaps across three different corporate accounts before writing the event out to all relevant parties. When you connect this via Vinkius, your agent gains immediate access to sophisticated scheduling logic without needing custom code for every single API in existence.
019d7616-6f17-7081-90b5-fb48a0a8d622 
How to set up Truto Unified Calendar MCP
The bottom line is that instead of writing code for Google's API or Microsoft's API separately, you just talk to your agent.
First, anchor this MCP instance to your local Vinkius agent. This tells your system where to look for scheduling data.
Next, provide the Master Token from Truto along with your integrated account ID, pointing it toward the specific calendar provider you need to query.
Finally, ask your assistant a natural language question like 'What time are we free next week?' and it handles the rest.
Who uses Truto Unified Calendar MCP
This MCP is essential for anyone whose job involves coordinating time across multiple people and systems. If you spend more than five minutes switching between calendar apps to book a meeting, this connector saves you hours.
You use this to schedule multi-provider meetings by telling your agent to check availability gaps across the CEO's Google account and the department’s Outlook group calendar in one go.
You force event creation directly into a client's varied infrastructure, without having to log into their fragmented Google or Microsoft portals yourself.
You centralize and manipulate the scheduling logic of your agent, enforcing calendar changes using one unified schema rule instead of multiple provider APIs.
Benefits of connecting Truto Unified Calendar MCP
Stop writing conditional code for different providers. This MCP gives you a single, normalized schema to read and write events against Google, Outlook, or any other connected service.
Instead of guessing if time slots are open, use the get_free_busy tool to accurately pinpoint available gaps in your schedule across multiple calendars instantly.
When an event changes—like a meeting moving from Google to Outlook—the system handles the write. Use update_event to modify details and sync them automatically everywhere.
If you need to know who was at last month's Q3 review, use list_events or get_event. It pulls all attendee lists, regardless of which calendar originally hosted the invite.
You can check if your company’s connection status is okay by running validate_connection, making sure no integrated account has been abruptly decoupled.
Truto Unified Calendar MCP use cases
Booking a cross-departmental meeting
The project manager needs to find 30 minutes next week when the Engineering team (on Google) and Marketing leadership (on Outlook) are both free. They ask their agent, which uses get_free_busy against both providers simultaneously, and gets a precise time slot.
Rescheduling client calls
A sales rep needs to change an event for a key client who uses a third-party calendar. The agent uses update_event, passing the new date and time, ensuring the change is reflected immediately without manual intervention.
Auditing account health
The IT admin needs to confirm that all 15 department calendars are still linked correctly. They run list_connections and receive a clear report on every provider's authentication status.
Capturing meeting details for records
After a major strategy session, the agent uses get_event to extract all granular metadata—like who was invited or if there’s an attached video link—so the notes are complete and accurate.
Truto Unified Calendar MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Treating APIs individually
Writing separate code blocks for Google Calendar API calls, followed by a completely different block of logic for Microsoft Graph API calls. This creates redundant error handling and complex branching.
Use this MCP to let your agent call unified functions like create_event or list_events. You write the command once, and the MCP handles routing it to the correct underlying provider.
Assuming data consistency
Running a scheduling script that assumes all calendar providers use the same metadata fields for attendees, which often leads to failed updates or missing information.
The MCP normalizes this. Use get_event to pull details into one schema, ensuring you always get key data points like attendee lists and locations consistently.
Ignoring connection status
Running a high-stakes scheduling query when an entire department's calendar connection has quietly dropped authentication. The script fails silently or throws vague errors.
Always start by calling list_connections and then use validate_connection. This confirms the account is ready to accept changes before you try to book anything.
When to use Truto Unified Calendar MCP
Use this MCP if your primary pain point is managing schedules across multiple, different calendar platforms (Google, Outlook, internal systems). You need a single source of truth for availability and event management. Don't use it if you only ever work within one specific platform; then, standard native SDKs might be fine. Also, don’t rely on this just to store contacts or simple notes—it is strictly a scheduling tool. For general data storage or CRM functions, look into dedicated record-keeping MCPs. If your goal is simply listing all calendars and seeing which ones are active, the list_calendars tool handles that initial check perfectly.
Frequently asked questions about Truto Unified Calendar MCP
How does the Truto Unified Calendar MCP handle different time zones? +
It normalizes all times to ISO-compliant formats, handling the complexity of multiple time zones so you don't have to worry about local offsets when scheduling.
Can I use this MCP to read old meeting details using the get_event tool? +
Yes, get_event pulls all rich metadata for a specific ID, giving you attendees, location data, and recurrence patterns, even if that information was added years ago.
Does Truto Unified Calendar MCP only work with Google or Outlook? +
No. The key feature is its unification layer; it treats all connected calendars—including those from other major providers—under one consistent schema.
What if I want to change a meeting after it was created? Do I use update_event? +
Yep. Use update_event and pass a JSON object with only the fields you need changed, like just updating the location or adding new attendees.
What is the difference between list_calendars and list_connections? +
Use list_connections to see if the account can connect (checking auth status). Use list_calendars once connected to get a list of actual, usable calendars under that account.