Truto Unified Calendar MCP. Manage time across Google, Outlook, and beyond.

Truto Unified Calendar MCP Server - Schedule & Sync Events

Your agent connects to one API layer that handles scheduling across Google, Outlook, and every major calendar provider you hook up. You don't gotta write separate logic for each system; your agent talks to Truto, and we handle the messy background work of translating those commands into whatever underlying API they need.

It’s simple: you give an instruction, and it posts live.

Setting Up Your Connections

First, you check what's linked up. You run list_connections to see exactly which provider types are attached and if the authentication status is current. If you need to confirm permissions on a specific account, you use validate_connection; this checks credentials and tells you if that API connection is actually accessible right now.

To map out all your options, run list_calendars. This pulls an inventory of every connected calendar across every provider, standardizing the data so you get one consistent schema regardless of whether it’s Google or something else.

If you need to know more about a specific calendar ID, you call get_calendar. It retrieves all the basic metadata for that single account and normalizes it into our unified Truto format.

Reading Event Data

When you're trying to figure out if a meeting can happen, you start with availability. You use get_free_busy by providing a date range; this checks the calendar for time blocks and returns clear segments marked as either free or busy in our standardized format. If you know an event ID, calling get_event pulls every granular detail about that specific meeting—it includes who's attending, where it is, and any provider-specific metadata like recurrence rules.

Want to see everything scheduled? You use list_events, feeding it a calendar ID. This gives you a list of all events on that calendar, showing titles, times, and attendees in one unified view. For a complete rundown of every single event associated with an account, run list_events against the entire calendar ID.

Modifying Your Schedule

You're ready to write something new? You use create_event. Just provide it with a calendar ID, a title, and the ISO 8601 start and end times. The event posts live right there to the provider you specified. If you gotta move or change an existing meeting, you call update_event. This takes the event ID and a JSON object containing only the fields that need changing—you don't send the whole thing again—and it pushes those changes live instantly.

If something gets canceled, you use delete_event. This removes an existing event from the specified calendar; remember, this action is irreversible. These tools mean your agent manages complexity so you can just tell it what you need done.