Google Calendar MCP
Google Calendar MCP server: list, read, create, update and delete events and calendars.
Documentation
Google Calendar MCP is a free MCP server that gives your AI agent two tools for reading your schedule and one admin tool for changing it. You can check what is coming up, book a meeting, or move one without leaving the editor. It is its own VS Code extension, it runs on your machine, and it talks to your own Google account.
There is no server to host and no config file to edit. You install the extension, sign in to Google once, and the Calendar tools appear in every agent it finds: VS Code Copilot, Claude Code, Cursor, OpenAI Codex, Google Gemini, Windsurf, Continue.dev, and Cline.
What you can ask
- “What meetings do I have today?”
- “Show me the details of my 3pm meeting”
- “Am I free on Friday afternoon?”
- “Book a 30 minute review with the team on Tuesday at 10”
- “Move the planning call to Thursday”
- “Which calendars do I have?”
The two Google Calendar MCP tools
| Tool | What it does | What you can pass |
|---|---|---|
calendar_list_events | List upcoming events with attendees, location, and times | A calendar, a start and end time, a result limit (25 by default), a text search |
calendar_get_event | Get the full details of one event | The event ID and, if needed, the calendar |
calendar_list_events reads your primary calendar from now onward unless you say otherwise. Name another calendar or a date range and the agent passes that along. Each attendee comes back with a response status, so “who has not accepted yet?” is a fair question.
The Calendar admin tool
Anything that changes your schedule goes through one admin tool with named actions.
| Action | What it does |
|---|---|
create_event | Create an event with a title, start, and end, plus an optional description, location, guest list, and time zone |
update_event | Change an event’s title, times, description, or location |
delete_event | Delete an event (needs confirmation) |
list_calendars | List all your calendars |
create_calendar | Create a new calendar |
Deleting an event needs explicit confirmation
The delete_event action only runs with confirm: true. The agent is told this up front, so it has to ask you before it removes a meeting. Reading events and listing calendars do not need it.
Three things people use it for
Planning the day from the editor
Ask what is on today and the agent lists your events with times and locations. Follow up with “what do I need to prepare for the 2pm?” and it reads that event’s description.
Booking time around work in progress
When you finish a branch and need a review, ask the agent to book 30 minutes with the reviewers. It creates the event with the guests you name, and it shows up on their calendars.
Release and deadline calendars
create_calendar makes a separate calendar for a project. The agent can then add milestones to it as you agree them, which keeps them out of your personal schedule.
Set it up in five steps
A setup wizard opens the first time you launch the extension. Most people pick OAuth, which works with a personal Google account and with a Google Workspace account.
- Create a project in the Google Cloud Console, or pick one you already have.
- Enable the Google Calendar API under APIs and Services.
- Create an OAuth client ID of type Desktop app.
- Paste the client ID and secret into the wizard.
- Sign in to Google in the browser window that opens, and authorize.
If your consent screen is set to External, add yourself as a test user first. Developers who already use the gcloud CLI can pick Application Default Credentials instead, and Workspace admins can use a service account key.
Using Google Calendar MCP with Claude Code, Cursor and other agents
You do not add a server entry by hand. The extension writes the registration for each agent it finds: ~/.claude.json for Claude Code, ~/.cursor/mcp.json for Cursor, ~/.codex/config.toml for OpenAI Codex, ~/.gemini/settings.json for Gemini, and the matching files for Windsurf, Continue.dev, and Cline. VS Code Copilot picks it up through the VS Code API.
Open a new session in any of them and the Calendar tools are in the tool list. If you only want some agents to have them, switch the others off in VS Code settings under gcalMcp.agents. The command “Google Calendar MCP: Remove from All Agents” takes every registration back out.
How it compares with Google’s own Calendar MCP server
Google now offers a remote Google Calendar MCP server as part of its Workspace MCP servers. It is in Developer Preview, so you need to join the Google Workspace Developer Preview Program and set it up through a Google Cloud project and the gcloud CLI.
| Google Calendar MCP (this extension) | Google’s Calendar MCP server | |
|---|---|---|
| Availability | Released, installs from the extension stores | Developer Preview |
| Where it runs | On your machine | Remote, hosted by Google |
| List, create, update, delete events | Yes | Yes |
| Create a calendar | Yes, create_calendar | Not listed |
| Suggest a meeting time | No | Yes, suggest_time |
| Accept or decline an invitation | No | Yes, respond_to_event |
| Agent setup | Automatic for eight agents | You configure each MCP client |
Google’s list was read from its developer documentation on November 12, 2026, and a preview can change.
Limits
- There is no free/busy tool. The agent answers “am I free?” by listing your events for that window.
update_eventchanges the title, times, description, and location. It does not change the guest list.- The agent cannot accept or decline invitations for you.
Common questions
Is Google Calendar MCP free?
Yes. The extension is free and MIT licensed.
Can it read more than one calendar?
Yes. list_calendars shows every calendar on your account, and the event tools accept a calendar ID, so you can ask about a shared or team calendar by name.
Does it handle time zones?
create_event accepts a time zone. If you do not give one, Google Calendar applies the calendar’s own.
Does it cover other Google services?
No. Google Calendar MCP covers Google Calendar only. Each service has its own extension: Gmail MCP, Google Drive MCP, Google Docs MCP, Google Sheets MCP. Google Workspace MCP bundles all five.
Where does my calendar data go?
Nowhere except Google. The MCP server runs on your own machine and calls the Google API with your credentials. There is no telemetry, and the sign-in token is kept in VS Code’s encrypted secret storage.
Use it without VS Code
Google Calendar MCP is also on npm, for Claude Code, Cursor, or any other MCP client. It needs Node.js 22 or newer.
npx -y @renzo.johnson/google-calendar-mcp
In Claude Code, one command adds it:
claude mcp add google-calendar-mcp -- npx -y @renzo.johnson/google-calendar-mcp
Outside VS Code there is no setup wizard, so the server takes your Google sign-in from the environment. It uses the first one it finds: an OAuth client ID, secret, and refresh token in GOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET, and GOOGLE_OAUTH_REFRESH_TOKEN; a key file named in GOOGLE_APPLICATION_CREDENTIALS; or the gcloud CLI’s Application Default Credentials. The npm package page has the config block for Claude Code and Cursor.
Install it
Google Calendar MCP is free and MIT licensed. It is its own extension, with only the Calendar tools. If you want Gmail, Calendar, Drive, Docs, and Sheets in one install, use Google Workspace MCP instead. Install one or the other, because both register the same Calendar tools.
- Install Google Calendar MCP from the VS Code Marketplace
- Install Google Calendar MCP from Open VSX for VSCodium, Cursor, and Windsurf
- Run Google Calendar MCP from npm with npx, in any MCP client
Listed in the official MCP Registry as com.renzojohnson/google-calendar-mcp.
Related
- Google Workspace MCP, all five Google services in one extension
- Gmail MCP, Google Drive MCP, Google Sheets MCP, and Google Docs MCP, the other service pages
- All Google MCP servers, the full list of 20