get_all_calendarsLABSCO SUMMARY
An agent can run your calendar day without you opening it.
"What's on today", "set up a standup with the engineering team tomorrow at ten", "cancel Friday at three" — each is one call. The Google OAuth is Nango's job rather than yours, which is the setup cost and the convenience in the same decision.
What it is
A Google Calendar client that takes its Google authorization through Nango rather than handling OAuth itself. It reads your calendars and events, creates Meet events with attendees, and cancels events.
What you get
- Every calendar you have access to
- Today's events, and upcoming events over a timeframe you choose
- Events inside a date range you name
- A Google Meet event created with its attendees
- An event cancelled
Requirements
Python 3.8 or newer, a Google account with Calendar access, and a Nango account — the server takes Nango's base URL, secret key, connection id and integration id from the environment, and Nango holds the Google OAuth.
Setup effort
One command plus a key — uvx git+https://github.com/Shameerpc5029/google-calendar-mcp.git, then supply credentials
USE CASES
01
Finding out what today looks like
Read back today's events in one call, before deciding what the rest of the day can hold.
02
Planning around the week ahead
Pull upcoming events over the timeframe you care about, or a specific date range when the question is narrower.
03
Setting up a meeting with a link already in it
Create the event with its attendees and get a Google Meet attached, rather than booking first and adding the link after.
04
Clearing something that is no longer happening
Find the event in the range you remember it being in, then cancel it.
05
Checking a calendar that is not your main one
List the calendars you can see, then read events from the one that actually holds the booking.
6 tools
Listed in project docs. Your client may show a different list.
get_calendar_eventscreate_meet_eventcancel_calendar_eventget_today_eventsget_upcoming_eventsBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- uvx on PATH
- Python 3.8 or later
- NANGO_NANGO_SECRET_KEY in your environment
- NANGO_CONNECTION_ID in your environment
- NANGO_INTEGRATION_ID in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx git+https://github.com/Shameerpc5029/google-calendar-mcp.gitMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"google-calendar": {
"command": "uvx",
"args": [
"git+https://github.com/Shameerpc5029/google-calendar-mcp.git"
],
"env": {
"NANGO_NANGO_BASE_URL": "https://api.nango.dev",
"NANGO_NANGO_SECRET_KEY": "<YOUR_NANGO_SECRET_KEY>",
"NANGO_CONNECTION_ID": "<YOUR_NANGO_CONNECTION_ID>",
"NANGO_INTEGRATION_ID": "<YOUR_NANGO_INTEGRATION_ID>"
}
}
}
}The three Nango values: <YOUR_NANGO_SECRET_KEY> is the secret key from your Nango project settings, <YOUR_NANGO_INTEGRATION_ID> the ID of the Google Calendar integration you add in the Nango dashboard, and <YOUR_NANGO_CONNECTION_ID> the connection ID Nango creates when you connect your Google account. Leave https://api.nango.dev as it is.
