list_calendarsLABSCO SUMMARY
Calendar writes, not just reads: the full create, edit and delete set.
Persistent token storage is the part that matters day to day, because you complete the Google consent flow once instead of on every session. The setup runs through the Google Cloud console first, enabling the API, configuring the consent screen and creating desktop credentials, before the first call works.
What it is
A TypeScript server for Google Calendar with OAuth and persistent token storage, covering calendars and the full event lifecycle.
What you get
- Every calendar the account can see (list_calendars)
- Events between two dates you name (list_calendar_events)
- One event in full (get_calendar_event)
- New events created, existing ones edited, and events deleted (create_calendar_event, edit_calendar_event, delete_calendar_event)
- Tokens stored after the first authorisation, so later sessions start already authenticated
- A Server-Sent Events transport as an alternative, selected with a launch flag
Requirements
Node.js v16 or higher and a Google Cloud project with the Google Calendar API enabled, an OAuth consent screen carrying the calendar.events scope, and desktop-app OAuth credentials. The downloaded credentials.json is pointed at with CREDENTIALS_PATH.
Setup effort
One command plus credentials — npx -y mcp-google-calendar, then supply credentials
USE CASES
01
Finding out what your week looks like
List the calendars the account can see, then pull the events between two dates.
02
Booking a meeting while you are still discussing it
Create the event from the details in the conversation rather than switching to the calendar UI.
03
Moving an event that clashes
Find the conflicting events in the range, then edit the one that has to move.
04
Reading the details of one invitation
Fetch the single event and read it in full instead of scanning a list.
05
Cancelling something you no longer need
Delete the event directly once you have confirmed which one it is.
6 tools
Listed in project docs. Your client may show a different list.
list_calendar_eventscreate_calendar_eventget_calendar_eventedit_calendar_eventdelete_calendar_eventBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- npx on PATH
- CREDENTIALS_PATH in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y mcp-google-calendarMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mcp-google-calendar": {
"command": "npx",
"args": [
"-y",
"mcp-google-calendar"
],
"env": {
"CREDENTIALS_PATH": "<YOUR_CREDENTIALS_PATH>"
}
}
}
}
