Multi-Calendar AI: Managing Personal, Work, and Side Project in One Prompt

Most people have at least two Google Calendar accounts: personal and work. Some have three (personal, work, side project). Managing them separately in an AI agent means either toggling between contexts or getting incomplete answers. CalendarMCP's multi-account feature lets you connect all of them under one API key and query across them with a single prompt.

The setup

Connect each Google account at calendarmcp.ai. The dashboard lets you add multiple Google accounts via OAuth and assign them readable names. One API key covers all of them.

Once you have multiple accounts connected, you can label them however makes sense. For this walkthrough, we will use three accounts:

• personal: personal@gmail.com (personal life, family, health)
• work: me@company.com (meetings, 1:1s, standups)
• project: me@myproject.io (launches, investor calls, side project milestones)

What the prompt looks like

With all three accounts connected, the most common query is just: "What do I have across all calendars next week?"

What do I have across all my calendars next week? 
Include personal, work, and project calendars. 
Show them in a single chronological list. 
Flag anything that overlaps across accounts.

CalendarMCP fans this out to three parallel list_events calls (one per account), returns the combined results, and the model merges them into a single view.

A real walkthrough

Here is what a full next-week query looks like from start to result.

The prompt

Check all three of my calendars (personal, work, project) for the week of June 2-6.
Show me:
1. Everything in one timeline
2. Any day where I have back-to-back meetings with no 15-minute buffer
3. Any day where I have nothing on the work calendar but something on personal or project 
   (potential flex days)
4. Days I need to prepare for something the following week

What the agent does

1. Calls list_events for personal account, June 2-6
2. Calls list_events for work account, June 2-6
3. Calls list_events for project account, June 2-6
4. Merges the three result sets, deduplicates any shared events, and generates the four-part analysis

What a real result looks like

WEEK OF JUNE 2-6

MONDAY, JUNE 2
09:00 [work] Eng standup (30min)
10:00 [work] Product review (1hr)
12:00 [personal] Dr appointment (1hr) ← personal
14:00 [work] 1:1 with manager (45min)
16:00 [project] Investor prep call (1hr)
⚠️ Back-to-back: 1:1 ends 14:45, nothing until 16:00 — that's fine

TUESDAY, JUNE 3
All day [personal] Jake's birthday 🎂
09:30 [work] Sprint planning (2hr)
14:00 [project] Beta launch review (1hr)
⚠️ Back-to-back risk: Sprint planning 09:30-11:30, make sure there's buffer before 14:00

WEDNESDAY, JUNE 4
No work calendar events — potential flex day
10:00 [personal] Dentist (1hr)
15:00 [project] Async review (no meeting block)

[... continues]

FLEX DAYS: Wednesday (no work meetings)

NEEDS PREP:
- Monday 16:00 investor prep call — review Q1 metrics beforehand
- Tuesday 14:00 beta launch review — check latest build status

NEXT WEEK PREP: Tuesday June 10 has a board update — suggest prepping materials Friday

Finding free time across all accounts at once

Single-account free-time search misses conflicts on other calendars. Multi-account search catches everything:

Find me three 90-minute slots next week where I have no events across ANY of my 
calendars (personal, work, project). Prefer mornings. Timezone: America/Los_Angeles.

This calls find_free_time with all accounts in scope, not just the primary one. You get slots that are genuinely open, not slots that look open on your work calendar but are blocked on your personal one.

Writing to the right account

When creating events, specify which account explicitly:

Create a 2-hour focus block on Thursday June 5 at 10am (America/Los_Angeles) 
on my WORK calendar. Title it "Deep work: auth system". Add no attendees.

Also create a reminder event on my PROJECT calendar for Friday June 6 at 5pm 
called "Launch checklist review".

The agent routes each create_event call to the correct account based on the natural language in your prompt.

Per-calendar permissions

CalendarMCP lets you set per-calendar read/write permissions when you connect each account. If you want the agent to see but never modify your personal calendar, set it to read-only. Your work and project calendars can stay read/write.

This is the right configuration for most people: read everything for context, only write to the calendars where you actually want automated event creation.

Why this matters

The alternative is switching context constantly. Query work calendar, switch account in your dashboard, query personal, open a third tab for the project account, try to hold the full picture in your head and make a scheduling decision. That is the current state for most people.

A single prompt with full multi-account context is not a productivity trick. It is just having one view of your actual schedule instead of three partial ones that you have to mentally merge.

Set up multi-account access at calendarmcp.ai. Add a second or third Google account in the dashboard, confirm the permissions, and your next prompt has access to all of them.