Think inside your AI world.
How do I connect Google Calendar to Claude?
Calendar over MCP means Claude can read the week as it actually is — events, free/busy across accounts, search — rather than as you remember it being.
Direct answer: connect Google Calendar over MCP in Claude — Settings → Connectors, authorise ('claude mcp add' in Claude Code). Claude reads calendars and events with filters, searches them, and checks free/busy across accounts. Scheduling questions and week-shape questions get answered from the source.
The week, read honestly
What is actually booked tomorrow, where the gaps are across both accounts, how much of the week is meetings versus held time — answered from the calendar rather than optimism. Cross-account free/busy is the sleeper feature for anyone juggling a company and a life.
The floor that meetings eat first
Worked case: you ratified a focus floor — mornings before 11 stay meeting-free four days a week, because a diary audit showed deep work was down to fragments and the product was paying for it. The calendar hosts whatever gets booked; defending Tuesday 9am is a policy about the calendar, not a feature of it.
The diary against the floor
Through Unl the week's read arrives measured: two morning slots breached — under your floor, the one the diary audit priced in lost product work. Scheduling requests get answered from the rule rather than from politeness. The floor holds because it shows up armed with its evidence.
Calendar to Claude reads the week you actually have; Calendar through Unl reads it against the time rules you ratified — the focus floor defends itself at booking time.
Reads through Unl arrive with measured context — in the presence of the decisions you’ve already settled. The reach lane is live: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.
Read further
Questions people ask
What does the Calendar MCP surface include?
Calendars and events with filters, event search, and free/busy across accounts — the observational layer scheduling decisions actually need.
Is time allocation really a criteria surface?
One of the most under-served ones: everyone has time rules — floors, caps, protected blocks — and almost nobody's tools know them. A ratified floor with its audit story turns every scheduling read into enforcement.
Does this work from other AI clients?
Yes — standard MCP; ChatGPT and others connect through their own flows with the same Google authorisation.
What this is
Think inside your AI world — you stay in command
Unlimitless (Unl to friends) holds what you've settled, reads what your tools are showing, and catches what's changed out in the world — and hands your AI whatever bears on the work, the moment it's needed, without you asking. The right thing, in front of the model, unprompted, with you in command of the call. So you keep moving toward what you set out to build, on top of everything you've already decided.
It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector. Quick to connect, in a couple of steps.
Unlimitless is open now to invited Alpha. Apply for the Beta waitlist to come in ahead of the full launch:
Alpha is invite-only · free at launch.