There are three ways to give an AI assistant your Google Calendar over MCP. You can switch on the built-in connector that Claude, ChatGPT and Cursor now each ship. You can point any MCP client at Google's own Calendar MCP server, which went into developer preview in April 2026. Or you can run a community server on your own machine. They differ less in what they can do than in who holds the OAuth client, which scopes you grant, and how much Google Cloud console you're willing to click through.

We build a remote MCP server that places phone calls, and "check my calendar, then call and book" is one of the most common things people ask an agent to do with it. So we set up each route, and on November 10, 2026 we probed Google's endpoint directly to see what it advertises before you sign in. This guide covers which route fits which person, the exact setup for each client, the scopes worth granting, and a deadline that lands on November 11.

Deadline: November 11, 2026. From that date, Google says its Workspace MCP servers "will reject requests from any app or integration whose OAuth client is not marked as agentic." If you already use Google's Calendar MCP server with your own OAuth client, open Google Auth Platform > Clients and tick Use this client for an AI-powered agent now. Google says clients not marked by November 12 "will remain non-agentic," and after that the only fix is a new OAuth client. This applies to OAuth clients you created; the built-in connectors covered below don't ask you for one.

Which Google Calendar MCP route to pick

An open ring-bound week planner showing Monday 16 to Sunday 22 August 2004 with ruled hourly lines and one handwritten entry on Wednesday
A paper week planner: the job a calendar MCP server hands to an agent. Photo by M.Minderhoud, CC BY-SA 3.0, via Wikimedia Commons (cropped).

Most people should start with the connector their assistant already has. Reach for the other two when you need a client the connectors don't cover, tighter control over scopes, or something running on your own hardware.

RouteBest forSetupWhere it runs
Built-in connector (Claude, ChatGPT, Cursor)Using your calendar inside one assistantOne click and a Google sign-inThe vendor's cloud, using the vendor's OAuth client
Google's Calendar MCP serverAny MCP client, one consistent tool set, Google-runGoogle Cloud project, consent screen, your own OAuth clientGoogle, at calendarmcp.googleapis.com
Community server (nspady, workspace-mcp)Local or self-hosted control, multiple accounts, extra toolsGoogle Cloud project, Desktop OAuth client, a local processYour machine or your own server
Automation platforms (Zapier, Composio, Pipedream)Calendar as one of many apps behind a single MCP URLAn account on the platformThe platform's cloud

One thing all four share: none of them changes what Google Calendar itself allows. The agent acts as you, with your permissions, so the scopes you grant are the real control. More on that below.

Google's official Calendar MCP server

Google announced the Calendar MCP server in developer preview on April 22, 2026, and its Workspace MCP page now lists separate servers for Gmail, Drive, Docs, Sheets, Slides, Chat and Classroom too. It's a remote server over Streamable HTTP at https://calendarmcp.googleapis.com/mcp/v1, and it uses Google's normal OAuth 2.0 sign-in. As of today it's still labeled "Developer Preview: Available as part of the Google Workspace Developer Preview Program," so expect changes and check that program's terms before building anything you depend on. Google hasn't published a price for the MCP server. Standard use of the Calendar API underneath costs nothing today, though Google says usage above a threshold of 1,000,000 requests a day per project will be billed, with details "later in 2026."

What the endpoint advertises, before you sign in

We sent it raw JSON-RPC with no credentials. Three things stood out.

First, initialize and tools/list both answer without a token. The server negotiated protocol version 2025-06-18, calls itself StatelessServer, and returned nine tools, each with annotations and an output schema. Only tools/call needs auth: an unauthenticated call to list_calendars came back as HTTP 401 with an isError result and a WWW-Authenticate header pointing at protected resource metadata.

Second, that metadata is per tool. The 401 for list_calendars points to /.well-known/oauth-protected-resource/list_calendars, and each tool's document lists the scopes that tool accepts. That's a neat way to tell a client the minimum it needs. Here's what each one said:

ToolRead-only hintScopes it accepts (any one)
list_calendarsYescalendar, calendar.readonly, calendar.calendarlist, calendar.calendarlist.readonly
list_events, get_event, search_eventsYescalendar, calendar.readonly, calendar.events, calendar.events.readonly
suggest_timeYescalendar, calendar.readonly, calendar.events, calendar.events.freebusy, calendar.freebusy
create_event, update_event, respond_to_eventNocalendar, calendar.events
delete_eventNo (marked destructive)calendar, calendar.events

All scopes start with https://www.googleapis.com/auth/. search_events is a semantic search over your primary calendar, and the list_events description tells the model to use it instead for open-ended keyword or topic searches. suggest_time takes attendee emails and a window and proposes slots across several calendars, which is the tool you want before booking anything.

Third, Google's authorization server doesn't offer dynamic client registration or Client ID Metadata Documents. Its metadata at accounts.google.com has no registration_endpoint. So an MCP client can't register itself on the fly the way it does with most remote servers. You create an OAuth client in Google Cloud and paste its ID and secret into your MCP client. Our MCP authorization guide explains why that's the "pre-registered client" path in the spec, and why most servers avoid it.

Setting it up

The steps are the same for every client up to the last one. You need membership in the Workspace Developer Preview Program and a Google Cloud project.

  1. Enable two APIs. gcloud services enable calendar-json.googleapis.com calendarmcp.googleapis.com --project=PROJECT_ID, or do it in the console. The first is the regular Calendar API; the second is the MCP service.
  2. Configure the consent screen in Google Auth Platform. Pick Internal if you're on Workspace and can; otherwise pick External and add yourself under Audience > Test users.
  3. Add scopes under Data Access. Google's page lists three read-only ones: calendar.calendarlist.readonly, calendar.events.freebusy and calendar.events.readonly. That's a good start, but per the table above it won't let the agent create or change anything. Add calendar.events if you want writes.
  4. Create the OAuth client: application type Web application, the redirect URI your MCP client uses, and Use this client for an AI-powered agent ticked. Google's MCP servers reject clients without it. Copy the client ID and secret.
  5. Add the server to your client with that ID and secret. Per-client details follow.

Two failure modes are worth knowing in advance. If you chose External and left the app in Testing, Google's OAuth docs say refresh tokens for that project expire after 7 days, so you'll be signing in weekly. The rule is specific to External apps in Testing, so an Internal Workspace app isn't affected. And if you're asked to sign in again roughly every hour, your client isn't getting a refresh token at all. Google issues one "only when the authorization request includes access_type=offline," and not every MCP client lets you add that parameter. If yours doesn't, Google's answer is to sign in again when the token expires.

Google Workspace MCP: one server per product

If you searched for a single "Google Workspace MCP" server, Google's design is the opposite. Its Workspace MCP page says "each Google Workspace product has its own dedicated MCP server," all in the same developer preview, all configured the same way. You add Calendar and Gmail as two connectors. The community workspace-mcp project is the main option that bundles everything behind one URL.

You may also see older guides recommend the gws command-line tool's MCP mode. It existed briefly: gws mcp shipped in v0.5.0 on March 5, 2026 and was removed in v0.8.0 as a breaking change. The project's README now says "This is not an officially supported Google product." Separately, the Gemini CLI Workspace extension runs a local MCP server with your own OAuth, if you live in Gemini CLI.

Google Calendar MCP in Claude

The built-in connector. In Claude on the web or the desktop app, go to Customize > Connectors, pick Google Calendar, click Connect and sign in to Google. Anthropic's help center says the Google Workspace connectors are "available for all users," while the connector's own docs page lists Pro, Max, Ultra, Team and Enterprise. On Team and Enterprise an Owner has to enable it for the organization first, and by default each action Claude takes needs your approval.

Can it write? Anthropic's pages disagree as of today. The help center lists "Create, update, and delete events," and the connector's marketplace listing shows nine tools whose names match Google's server exactly, including create_event and delete_event. The docs page still says "Claude reads your calendar only." Check the tool list under Customize > Connectors on your own account rather than trusting either page.

Google's server as a custom connector. If you want your own OAuth client and scopes instead, Google documents this path. Create the OAuth client with redirect URI https://claude.ai/api/mcp/auth_callback. Then, under Settings > Connectors, click Add custom connector, enter https://calendarmcp.googleapis.com/mcp/v1, and put the client ID and secret under Advanced settings. Google says this needs a Pro, Max, Team or Enterprise plan. Our guide to adding an MCP server to Claude covers the connector screens in more detail.

Claude Code. If you sign in to Claude Code with a claude.ai account, connectors you added in claude.ai show up there automatically. To use Google's server with your own client instead, register http://localhost:8080/callback on the OAuth client and add it with a fixed callback port:

claude mcp add --transport http \
  --client-id YOUR_CLIENT_ID --client-secret --callback-port 8080 \
  google-calendar https://calendarmcp.googleapis.com/mcp/v1

--client-secret prompts for the secret and stores it in the system keychain on macOS, or a credentials file elsewhere. Run /mcp to sign in. If sign-in fails with a redirect mismatch on Claude Code v2.1.229, upgrade: that version sent 127.0.0.1 instead of localhost. More on scopes and flags in our Claude Code MCP setup guide.

Google Calendar MCP in ChatGPT

ChatGPT's Google Calendar app (connectors are now listed under Settings > Plugins) arrived on August 25, 2025, and gained write actions on March 13, 2026. In a Business or Enterprise workspace, OpenAI's release notes say write actions "remain disabled by default until workspace admins enable them," per app. The app requests calendar.events plus a read-only Google Meet scope for meeting lookups. Since August 28, 2026 you can connect more than one Google account on Plus, Pro, Business and Enterprise. OpenAI's general caveat for apps also applies: some "may not be available in certain regions (including the EEA, GB, or Switzerland)."

Connecting Google's own MCP server to ChatGPT is less clear. OpenAI's help center says custom MCP connections "are available for ChatGPT Business and Enterprise/Edu customers on ChatGPT web" (personal plans have had a developer mode, so check your own settings), and Google hasn't published ChatGPT-specific steps or a redirect URI. For most people the built-in app is the answer. If you're adding other servers, our ChatGPT MCP guide walks through developer mode and custom connectors.

Google Calendar MCP in Cursor

Cursor shipped its own Google Calendar plugin on August 3, 2026, described as able to "read schedules, create and update events, find free time." Install it from the marketplace or type /add-plugin google-calendar. One gap remains: a Cursor staff member wrote on October 11 that "the actual sign-in Google needs isn't supported in the CLI yet," so the plugin works in the desktop app but not in the CLI agent.

To use Google's server instead, add it to ~/.cursor/mcp.json (or a project's .cursor/mcp.json) with static OAuth credentials, and register http://localhost:8787/callback, Cursor's desktop redirect, on the OAuth client:

{
  "mcpServers": {
    "google-calendar": {
      "url": "https://calendarmcp.googleapis.com/mcp/v1",
      "auth": {
        "CLIENT_ID": "${env:GCAL_CLIENT_ID}",
        "CLIENT_SECRET": "${env:GCAL_CLIENT_SECRET}",
        "scopes": [
          "https://www.googleapis.com/auth/calendar.events",
          "https://www.googleapis.com/auth/calendar.calendarlist.readonly"
        ]
      }
    }
  }
}

Set scopes explicitly; otherwise Cursor tries to discover them from the authorization server. Google's Cloud MCP release notes record that Cursor's desktop redirect didn't work with Google's MCP servers in June and was fixed on July 22, 2026, so update Cursor if sign-in fails with a redirect error. Google doesn't document Cursor for the Calendar server specifically; this follows Cursor's documented static-OAuth format.

Community servers: when local is the better choice

Two open-source servers stand out by GitHub stars, and both use an OAuth client you create in Google Cloud. Each one gets you something the hosted options don't.

  • nspady/google-calendar-mcp (npm @cocal/google-calendar-mcp, v2.8.1, MIT, about 1,200 GitHub stars). Thirteen tools, including batch create-events, get-freebusy and get-current-time. Its standout feature is multiple accounts: "Connect multiple Google accounts (e.g., work, personal) and query them simultaneously." It can also run over HTTP or in Docker.
  • taylorwilsdon/google_workspace_mcp (PyPI workspace-mcp, v2.4.0, MIT, about 3,500 stars). One server for all of Workspace, with tool tiers, a --read-only flag, --tools calendar to load only Calendar, and OAuth 2.1 multi-user auth when you run it over Streamable HTTP. Its extended Calendar tier adds out-of-office and focus-time tools.

The nspady setup is typical. Create a Google Cloud project with the Calendar API enabled, make an OAuth client of type Desktop app (the README marks this "Important!"), add yourself as a test user, download the credentials JSON, and point the server at it:

{
  "mcpServers": {
    "google-calendar": {
      "command": "npx",
      "args": ["@cocal/google-calendar-mcp"],
      "env": { "GOOGLE_OAUTH_CREDENTIALS": "/path/to/gcp-oauth.keys.json" }
    }
  }
}

Then ask your assistant to authenticate. The same 7-day rule applies here: the README warns, "If you're in test mode (default), tokens expire after 7 days." Re-run npx @cocal/google-calendar-mcp auth when that happens. A local stdio server works in Claude Desktop, Claude Code, Cursor and VS Code, but not in claude.ai on the web or ChatGPT, which only connect to remote URLs. Our explainer on remote vs local MCP servers covers that split.

If you'd rather not touch Google Cloud at all, Zapier MCP exposes Google Calendar actions such as Quick Add Event and Add Attendee(s), Composio lists a Google Calendar toolkit of 47 tools, and Pipedream offers one too. You trade setup for a third party holding your Google token, and each prices usage its own way. Our Zapier MCP guide explains how its task billing works.

Scopes: read-only vs write

Whatever route you take, the OAuth scopes decide what an agent can do, and Google's scopes are finer-grained than most people realise. These are the ones that matter for an assistant, with Google's own descriptions:

ScopeGoogle's description
calendar.events.freebusy"See the availability on Google calendars you have access to."
calendar.events.readonly"View events on all your calendars."
calendar.calendarlist.readonly"See the list of Google calendars you're subscribed to."
calendar.events.owned"See, create, change, and delete events on Google calendars you own."
calendar.events"View and edit events on all your calendars."
calendar"See, edit, share, and permanently delete all the calendars you can access using Google Calendar."

Start with the first three; that's read-only and enough for "what's on Thursday?" or "when am I free next week?". Add calendar.events when you want the agent to book things. Avoid the full calendar scope unless you genuinely need the agent to share or delete whole calendars, because that's what it permits. Google's own advice is to "choose the most narrowly focused scope possible," and reading calendar events already counts as a sensitive scope that needs Google's review before an app can go public.

Quotas rarely matter for one person, but they're worth knowing if you script an agent across a team. For Cloud projects created on or after May 1, 2026, the Calendar API allows 600 requests per minute per user and 10,000 per minute per project.

Security: your calendar is an inbox anyone can write to

The part people miss is that strangers can put text on your calendar. Anyone with your address can send an invite, and under Google Calendar's "From everyone" setting it's added to your calendar automatically. When an agent reads your schedule, it reads that text too.

This has been demonstrated. In August 2025, researchers from Tel Aviv University, the Technion and SafeBreach presented "Invitation Is All You Need" at Black Hat USA. A poisoned event title hijacked Gemini for Workspace when the victim simply asked for a summary of their day, and the paper describes 14 attack scenarios, from deleting events to controlling smart-home devices. Google says it rolled out mitigations. Its Calendar MCP page now carries an explicit warning about indirect prompt injection and advises: "Avoid asking your MCP client to process events or other resources from unverified sources."

What helps in practice:

  • Keep tool approvals on for write tools. Claude asks by default; don't switch delete_event to always-allow.
  • Grant read-only scopes to agents that only need to read.
  • Be wary of combining a calendar server with tools that send data out (email, web requests) in the same session without review.
  • In Google Calendar, set Settings > Event settings > Add invitations to my calendar to "Only if the sender is known."

Our MCP security guide covers tool poisoning and prompt injection in more depth.

From "when am I free?" to a booked appointment

A calendar server tells an agent when you're free. Plenty of the things that need to go on the calendar, like a dentist cleaning, a vet visit or a contractor quote, still get booked by phone. That's where a second server comes in, and it's the combination we see most with DialMCP.

The agent does the orchestration; the two servers never talk to each other. With Google Calendar and DialMCP both connected, a single request runs like this:

  1. You ask: "Book my dental cleaning for a weekday morning in the next two weeks."
  2. The agent calls list_events or suggest_time on the calendar server and finds three open mornings.
  3. It calls DialMCP's place_call with the clinic's number and an objective that lists those exact windows and what to accept as a fallback. The call goes out from your own verified number, the voice agent says up front that it's an AI calling for you, and it waits through the phone menu and hold.
  4. It polls get_call until the call ends and reads the structured result: achieved or not, the time agreed, anything the clinic asked you to bring.
  5. With a write scope and your approval, it calls create_event for the confirmed slot.

DialMCP has no Calendar integration of its own and doesn't need one; MCP lets the agent combine the two. Calls go to US and Canadian numbers between 8am and 9pm in the destination's local time. The full call contract is on our tool reference, and how to make a phone call with an AI assistant walks through the setup.

Further reading

Try a remote MCP server that does real work. DialMCP lets Claude, ChatGPT, Codex, Cursor or VS Code place real phone calls from your own verified number and hand back a transcript and a structured outcome. Add https://mcp.dialmcp.com/mcp as a connector and sign in. US and Canada, free during launch.

Connect DialMCP to your client

FAQ

Is there an official Google Calendar MCP server?

Yes. Google runs a remote Calendar MCP server at https://calendarmcp.googleapis.com/mcp/v1, announced in developer preview on April 22, 2026. It uses Streamable HTTP and Google OAuth, and offers nine tools including list_events, suggest_time and create_event. As of November 10, 2026 it requires the Google Workspace Developer Preview Program and your own OAuth client from a Google Cloud project.

Can Claude add events to my Google Calendar?

Probably, but check your account. Anthropic's help center says the built-in Google Calendar connector can create, update and delete events, and its tool list includes create_event, while the connector's docs page still says it only reads. Look at the tools listed under Customize > Connectors. By default Claude asks for your approval before each action.

Why does Google Calendar MCP ask me to sign in again every week?

If your Google Cloud consent screen uses the External user type and the app is still in Testing, Google issues refresh tokens that expire after 7 days. The rule doesn't apply to Internal (Workspace) apps or to apps that are no longer in Testing. If you're asked roughly every hour instead, your client isn't requesting access_type=offline, so it never gets a refresh token.

What does 'Use this client for an AI-powered agent' mean?

It's a setting on OAuth clients in Google Auth Platform > Clients. From November 11, 2026, Google Workspace MCP servers reject requests from OAuth clients that don't have it selected, and Google says clients not marked by November 12 stay non-agentic, so after that you need a new OAuth client. Tick it on the client you use with the Calendar MCP server.

Which scopes should I grant a Google Calendar MCP server?

For read-only use, calendar.events.readonly, calendar.calendarlist.readonly and calendar.events.freebusy are enough. Add calendar.events when you want the agent to create or change events. Avoid the full calendar scope unless the agent needs to share or delete whole calendars.

Is there a Google Workspace MCP server that covers Gmail, Drive and Calendar together?

Not from Google. Google runs a separate MCP server for each Workspace product, so you add Calendar and Gmail as two connectors. The open-source workspace-mcp project bundles Gmail, Drive, Calendar and more behind one server, locally or over Streamable HTTP.