Google Calendar

io.github.domdomeggPublished by GitHub account domdomeggv1.1.3Updated Oct 24, 2026

Allow AI systems to list, create, update, and manage Google Calendar events.

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Local MCP server that connects an assistant to Google Calendar so it can list, create, update, move and delete events and check availability.

What you can do
  • List calendars, subscribe to shared ones, update calendar settings and unsubscribe
  • List, search and read events in a time range, including recurring event instances
  • Create, update, move and delete events, with attendees and Meet links
  • RSVP to invitations and query free/busy times for scheduling
  • List calendar access permissions and fetch the available color palette
When to use it
Useful when you want an assistant to work with your own Google Calendar: scheduling meetings, answering what is on today, finding free slots, rescheduling, blocking focus time or responding to invitations.
Requirements
Runs locally via npx (Node.js) and acts as an OAuth proxy to Google, listening on localhost port 3000 by default. Needs a Google Cloud project with the Calendar API enabled and an OAuth client, plus GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_ACCESS_TOKEN and MCP_TRANSPORT set. Desktop client only.
Before you install
Requires Google OAuth client credentials and an access token with full calendar scopes, so treat them as secrets. The assistant can create, change, move and delete events and send invites or RSVPs on your behalf, which notifies attendees. The server proxies OAuth requests to Google and passes your bearer token through to the Calendar API.

Installation

In SourceWeft

  1. Open Google Calendar in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

google-cal-mcp

MCP server for Google Calendar - list, create, update, and manage calendar events.

Use Cases

Schedule meetings: "Set up a 30-min sync with Sarah next week" → finds a free slot, creates the event with a Meet link, and sends the invite.

RSVP to invites: "Accept the team offsite but decline the vendor demo" → responds to pending invitations automatically.

Find availability: "When am I free this Thursday afternoon?" → queries your calendar and returns open slots.

Reschedule events: "Move my 1:1 with Alex to Friday at 2pm" → updates the event and notifies attendees.

Daily briefing: "What's on my calendar today?" → lists all events with times, locations, and attendees.

Block focus time: "Block 2 hours tomorrow morning for deep work" → creates a calendar event to protect your time.

(These are just examples - any workflow that needs calendar access can use this.)

Setup

1. Create Google OAuth credentials

  1. Go to Google Cloud Console
  2. Create a new project (or use existing)
  3. Enable the Google Calendar API
  4. Go to APIs & Services → OAuth consent screen, set up consent screen
  5. Go to APIs & Services → Credentials → Create Credentials → OAuth client ID
  6. Choose Web application
  7. Add http://localhost:3000/callback to Authorized redirect URIs
  8. Note your Client ID and Client Secret

2. Run the server

bash
GOOGLE_CLIENT_ID='your-client-id' \GOOGLE_CLIENT_SECRET='your-client-secret' \MCP_TRANSPORT=http \npm start

The server runs on http://localhost:3000 by default. Change with PORT=3001.

3. Add to your MCP client

With the server running, follow the instructions on install-mcp, which generates the right config for your MCP client (Claude Code, Claude Desktop, Cursor, Cline, VS Code, and more).

Architecture

This server acts as an OAuth proxy to Google:

mermaid
graph LR    A[MCP client] <--> B[google-cal-mcp] <--> C[Google OAuth/API]
  1. Server advertises itself as an OAuth authorization server via /.well-known/oauth-authorization-server
  2. /register returns the Google OAuth client credentials
  3. /authorize redirects to Google, encoding the client's callback URL in state
  4. /callback receives the code from Google and forwards to the client's callback
  5. /token proxies token requests to Google, injecting client credentials
  6. /mcp handles MCP requests, using the bearer token to call Calendar API

The server holds no tokens or state - it just proxies OAuth to Google.

Tools

ToolDescription
Calendars
calendars_listList all calendars the user has access to
calendarlist_insertSubscribe to a shared calendar
calendarlist_updateUpdate calendar settings (color, visibility, reminders)
calendarlist_deleteUnsubscribe from a calendar
Events
events_listList events in a time range with search/filter
event_getGet details of a specific event
event_createCreate a new event with attendees and Meet link
event_updateUpdate an existing event
event_deleteDelete an event
event_respondRSVP to an invitation (accept/decline/tentative)
event_moveMove event to a different calendar
event_instancesGet instances of a recurring event
Availability
freebusy_queryFind free/busy times for scheduling
Sharing
acl_listList who has access to a calendar
Colors
colors_getGet available color palette for calendars/events

Calendar API Scopes

  • calendar - Full access to calendars
  • calendar.events - Read/write events

Contributing

Pull requests are welcomed on GitHub! To get started:

  1. Install Git and Node.js
  2. Clone the repository
  3. Install dependencies with npm install
  4. Run npm run test to run tests
  5. Build with npm run build

Releases

Versions follow the semantic versioning spec.

To release:

  1. Use npm version <major | minor | patch> to bump the version
  2. Run git push --follow-tags to push with tags
  3. Wait for GitHub Actions to publish to the NPM registry.

Source: README.md at commit 42d8573

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.3LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.