← Blog
ai-assistantproductivitytutorialclaude

Build an AI Executive Assistant with Calendar Access (in an Afternoon)

A practical recipe for turning Claude into the assistant that actually manages your day. Covers prompt structure, the calendar tools that matter most, and the boring guardrails that keep it from double-booking you.

Sarah Chen
Developer Relations, CalendarMCP ·

Most people use Claude as a fancy chat box. Hand it your calendar and a few sensible rules and it turns into something different: an actual executive assistant that books your week instead of just talking about it.

This is a practical recipe. No vendor pitch about agentic this and intelligent that. Just the prompt structure, the tools that earn their keep, and the dumb guardrails that stop your assistant from double-booking your dentist.

What you actually need

  • A Claude account (Claude.ai, Claude Desktop, or Claude Code all work)
  • A CalendarMCP API key connected to your Google Calendar
  • A short system prompt that defines what the assistant is allowed to do
  • A bit of patience the first week to correct it when it gets a tone wrong

That is the whole stack. The afternoon part is real. You can be running by lunch and refining for a week.

The system prompt

Most assistant projects fail because the prompt is one of two things: empty, or a 4,000-word essay about being helpful. Neither works. Aim for short, opinionated, and rule-driven.

Example system prompt

You are my executive assistant. You manage my Google Calendar via CalendarMCP.

Hard rules:
- Never schedule between 12:00pm and 1:00pm (lunch).
- Never schedule before 9:00am or after 6:00pm Pacific without explicit go-ahead.
- Always leave 15 minutes between meetings.
- For external invites, default to Google Meet unless I say otherwise.
- Confirm before any action that creates, moves, or deletes more than 3 events.

Defaults:
- Time zone: America/Los_Angeles.
- New 1:1s are 30 minutes. New team meetings are 45.
- Travel days = block whole day, mark "out of office".

When I ask vague things ("free time next week"), check the calendar first, propose 3 slots, then ask.

That is roughly 150 words and it covers 90 percent of real interactions. Every line is there because something went wrong without it. Claude with no rules will book 7am calls. With these rules, it will not.

The tools that matter most

CalendarMCP exposes ten calendar tools. For an executive-assistant use case, four of them carry almost all the weight.

list_events

The bread and butter. Used every time the assistant needs to know what your week looks like before it commits to anything new. Multi-calendar fan-out matters here. If you have a personal and work calendar, you want both checked at once.

find_free_time

For "find me 3 slots Wednesday afternoon to talk to Mark" prompts. Returns gaps that match a duration. Saves the assistant from guessing.

create_event

The action verb. Combine with attendee emails and you get a real calendar invite, complete with Meet link. Pair with the system-prompt rule that requires confirmation when the action is non-trivial.

update_event

For "push my 2pm to 3pm" or "make the standup recurring weekly". Used a lot more than you would expect. Real life is mostly rescheduling, not scheduling.

The other six tools (get_event, delete_event, quick_add, batch_update, list_calendars, manage_attendees) come up enough to be worth having, but they are the supporting cast.

Three flows that pay for themselves

Morning briefing

"Give me the day. What's on my calendar, who's external, what should I prep for?"

The assistant reads your calendar, separates internal from external meetings, and flags anything that needs prep (decks, decisions, awkward conversations). One prompt replaces the 5 minutes you spent staring at the day view.

Reschedule cascade

"I just got pulled into a 2pm. Reschedule everything that conflicts."

With a single prompt, the assistant identifies conflicts, finds new slots, sends polite update notes to the affected people, and confirms the moves. This is the killer feature. Anyone who has rescheduled four meetings in a row knows why.

Travel mode

"I'm in Tokyo May 6 to May 12. Block out travel days, shift my 1:1s to async, no calls before 10am Tokyo time."

Combine with batch_update and the assistant rewrites your week in one shot. The kind of thing that used to take 20 minutes of careful clicking.

The boring guardrails

This is the part most tutorials skip. It is also the part that turns a fun demo into a tool you actually trust.

  • Confirm before bulk actions. Anything touching more than 3 events should ask first. Saves you from the day Claude misreads "delete next week's syncs" as "delete next month's".
  • Per-calendar permissions. CalendarMCP lets you mark calendars as read-only. Use it. Your spouse's shared calendar should never be writable from your assistant.
  • A weekly review. Once a week, ask the assistant to summarise what it did. You will catch quirks early.
  • Test on a junk calendar first. Make a calendar called "AI Sandbox" and let the assistant practice there for a day before unleashing it on your real schedule.

What does not work yet

Honesty is part of trust. A few things still need a human:

  • Negotiating across other people's calendars when you do not have visibility into them.
  • Tonally tricky cancellations ("sorry, can't make our anniversary dinner").
  • Anything where you want plausible deniability ("I wish I could but I'm double-booked").

For the other 80 percent of calendar work, an AI executive assistant with calendar access is the rare productivity upgrade that pays back the afternoon you spent setting it up. Try it. Your calendar will look a lot less hostile by Friday.

Ready to get started?

Connect your Google Calendar to Claude and any MCP client in about two minutes.

Connect Google Calendar