MCP connectorsGoogle Calendar

Google Calendar MCP: connect Google Calendar to Claude and ChatGPT

Ask Claude or ChatGPT what your week looks like, when you last met Acme, or to put a planning session in on Thursday afternoon. The answer comes straight from Google Calendar, with a link to the event.

With Deployed OS everyone connects their own Google account. The AI sees the calendars that person can open, and new events are added without a single invitation email.

2 read actions · 1 write action · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with Google Calendar in Claude and ChatGPT

Management

The week before it starts

Every meeting next week, how many hours they add up to and where the gaps are. Asked on Friday afternoon, planned before Monday.

Sales

Know who is in the room

Open tomorrow’s customer meeting, see who accepted and read the agenda in the description. Then ask for three questions to bring.

Projects

Find the date it happened

When did we last meet the supplier, and who was there? Search the calendar by words instead of scrolling back through months.

Everyone

Book it in one sentence

Say what, when and with whom. The AI confirms title, time and attendees, then puts it in your calendar without emailing anyone.

Examples

Ask it like this

“What does my Thursday look like, and where can I fit a 45-minute call?”
“When did we last meet Nordic Freight, and who attended?”
“List every meeting next week with guests from outside the company.”
“How many hours of meetings did I have this month compared with last month?”
“Read the description of tomorrow’s board meeting and summarise the agenda.”
“Book ‘Q4 planning’ on Wednesday from 2 pm to 3:30 pm with Sara and Jonas.”

The connector

What the Google Calendar MCP connector does today

Readscalendar_list_events
Lists the events in your calendar between two dates up to 92 days apart, with recurring events shown one by one. Can filter on words, and uses your main calendar unless you name another one you can open.
Readscalendar_get_event
Reads one event with its attendees and their replies, location and description.
Writescalendar_create_event
Creates an event in your calendar once you have confirmed title, time and attendees. Attendees are added without invitation emails.

Need it to do more? We extend connectors for the companies that use them.

Security

Who sees what

Reads events, creates events: The connector reads your calendars and creates new events. It cannot change, move or delete an existing event, and it sends no invitation emails.
Each person’s own calendar: Everyone connects their own Google account. The AI sees the calendars that person can open, with the same detail they would see themselves.
You choose who gets it: Admins decide which groups at the company can use the Google Calendar connector, and which of them may also create events. Everyone else never sees it.
Every call logged: Who looked, who booked, when. Deployed OS shows reads and writes per connector and per person, the log can be exported, and access is revoked centrally the day someone leaves.

Setup

Set up the Google Calendar connector in three steps

An admin creates a project in your company’s Google Cloud, sets up an internal OAuth app and turns on the Calendar API. The same Google app serves Gmail, Drive, Analytics and Ads, and your company owns it.

The admin adds the app’s Client ID and Client secret to Deployed OS and chooses which groups get Google Calendar.

Each person connects their own Google work account. Then they ask about their week in Claude, ChatGPT or Copilot.

Compared

Google Calendar’s own MCP server or Deployed OS?

Google runs its own remote MCP servers for Calendar, Gmail and Drive. A developer turns them on in a Google Cloud project and connects an AI client. For one person, or a developer building an agent, that is a good fit.

Deployed OS is built for the whole company: one connection for Google Calendar and the rest of your tools, each person’s own login, admins choosing which groups get what, and a log of every call. The same connection works in Claude, ChatGPT and Copilot, next to your company’s skills and guardrails.

Their documentation: Google’s MCP server

Questions

Google Calendar MCP: common questions

Yes. Google runs remote MCP servers for Calendar, Gmail and Drive that a developer sets up in a Google Cloud project. Deployed OS gives the whole company one connection instead, with each person’s own login, access per group and a log of every call.

No. It reads events and creates new ones. Existing meetings are never moved, changed or deleted. If you want it to do more, for example reschedule meetings, we can extend it for you.

No. Attendees are added without invitation emails, and whether the event shows in their calendar depends on their own Google Calendar settings. If you want them notified, send the update from Google Calendar.

Only the ones you can already open in Google Calendar, with the same detail you see there. The AI always works as you, never as an admin.

Yes. Deployed OS is your company’s own Google Calendar MCP server, so the same connection works in Claude, ChatGPT and Copilot. People keep the assistant they prefer.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors

Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.

You’ll hear from Poyan Karimi

Co-founder · Deployed AI