Google Calendar MCP Integration

Weldable's Google Calendar MCP integration gives your AI agent full access to your schedule. Ask Claude to check your availability, create events, find meeting times, or reschedule conflicts, all through natural language. Connect once via OAuth and your agent gets 9 calendar actions covering events, availability, and multi-calendar management.

Calendar is where scheduling meets context. An AI agent that can read your schedule and act on it turns routine coordination into something that happens in the background while you work.

Use cases

Meeting prep briefings

Your agent checks tomorrow's calendar each evening, pulls the attendee list for each meeting, and assembles relevant context. For a sales call, it grabs the latest deal notes from your CRM. For a 1:1, it surfaces action items from the last meeting's notes. The briefing lands in your inbox or Slack before you start your day.

Cross-calendar scheduling

Finding a time across three busy people usually means fifteen minutes of tab-switching. Your agent queries free/busy data for all participants at once, identifies overlapping open slots, and creates the event with the right attendees and a video link. Tell it "find 30 minutes for me, Sarah, and Dev this week" and it handles the rest.

Schedule-aware notifications

Pair Google Calendar with Slack or Gmail to send context-aware alerts. Your agent checks your calendar before sending a Slack reminder about a deadline. If you're in back-to-back meetings until 3pm, it delays the notification. If you have a free slot at 11am, it nudges you then.

Automated time blocking

Tell your agent to block two hours of focus time every day this week. It scans your existing events, finds gaps that fit, and creates calendar entries with the right title and color. If something gets scheduled over a focus block later, a workflow can detect the conflict and move the block to the next available slot.

Recurring event cleanup

Your agent searches for recurring meetings, checks attendance patterns from the last month, and flags ones where half the invitees regularly decline. It posts a summary to Slack asking if those meetings should be shortened, moved, or cancelled entirely.

How it works

Connect your Google account through a one-click OAuth flow. Weldable requests calendar permissions and handles token refresh automatically, so expired credentials are never your problem.

Once connected, talk to your agent in plain English. Say "what do I have tomorrow afternoon" and Weldable matches your intent to the right Calendar API call, sets the correct time range, and returns your events. Your agent can chain actions too: check availability, find an open slot, create an event, and add attendees in a single conversation turn.

For workflows, calendar actions combine with other integrations. A scheduled workflow can pull your day's agenda every morning and post it to Slack. An event-driven workflow can prepare meeting notes in Google Docs whenever a new meeting appears on your calendar.

Tips

Always include a timezone in event creation. Google Calendar API defaults to UTC when no timezone is specified. If your agent creates a "3pm meeting" without a timezone, it lands at 3pm UTC, which is probably not what you meant. Weldable passes timezone data when you provide it, so say "3pm Eastern" or "3pm in America/New_York" to be explicit.

Use free/busy queries instead of listing events to check availability. The free/busy endpoint returns just busy time blocks without exposing event details. This matters when checking other people's calendars, as you can see when they're available without reading their private meeting titles.

Set singleEvents to true when listing events. Without this flag, recurring events return as a single entry with recurrence rules instead of individual instances. Your agent needs individual instances to answer questions like "what meetings do I have this Thursday" accurately.

Quick add handles natural language dates well. The quick add endpoint parses strings like "Lunch with Jamie next Tuesday at noon at Flour Bakery" into a properly structured event. Use it for fast, informal scheduling where you don't need to set reminders or custom colors.

All-day events use date, not dateTime. This is a common Calendar API gotcha. Timed events use dateTime with an RFC3339 timestamp, but all-day events use date with a simple YYYY-MM-DD string. Mixing these up produces API errors. When telling your agent to create an all-day event, say "all-day" explicitly so it picks the right format.

Free/busy responses come back in UTC. Even if you set a timezone on the request, the busy intervals in the response use UTC timestamps. Your agent handles the conversion, but keep this in mind if you're inspecting raw API responses in workflow logs.