Connect Google Calendar to Claude Code

Have Claude create events and reschedule meetings in Google Calendar. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Google Calendar to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Google Calendar, you add a Google Calendar MCP server: a small hosted service that exposes Google Calendar's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Google Calendar account. No API keys pasted into config files.

claude mcp add --transport http google-calendar https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Google Calendar once connected?

Full read-write Google Calendar access lets Claude create events with the right guests and conferencing, reschedule or update existing events, manage RSVPs, and block focus time across the calendars you connect, once you approve. The back-and-forth that used to mean manual entry happens where the schedule already lives.

Create an event with the right guests, location, and a Google Meet link
Reschedule or update an existing event and notify attendees
Find a free slot across attendees and propose a time to book
Add or remove guests and update your RSVP on an invitation
Block focus time or hold tentative slots on your calendar
Cancel or delete an event after you approve it

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Google Calendar access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Google Calendar API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Google Calendar changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Google Calendar connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Google Calendar connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Google Calendar account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Google Calendar's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Google Calendar?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Google Calendar account it signs in with. Revoking access is one click in Google Calendar.

More on the Google Calendar connector

Google Calendar connector for claude.ai Calendly + Claude Code Outlook + Claude Code Cal.com + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us