Google Calendar MCP Server

What is Google Calendar MCP Server?

The Google Calendar MCP Server provides integration with Google Calendar, allowing Claude to view, create, and manage calendar events through the Model Context Protocol. It is intended for users who want AI assistants to interact with their Google Calendar data.

How to use Google Calendar MCP Server?

Install Node.js 16+, set up a Google Cloud project with the Calendar API enabled, create OAuth 2.0 credentials (Desktop app type), and download the credentials as gcp-oauth.keys.json in the project root. Install dependencies with npm install, build with npm run build, then configure the server in your Claude MCP settings file with the command node and the path to the built index.js. On first run, the server opens a browser for OAuth authentication, then saves tokens in .gcp-saved-tokens.json. The available tools are list-calendars, list-events, create-event, update-event, and delete-event.

Key features of Google Calendar MCP Server

• List all available calendars
• List events from a specific calendar
• Create new calendar events
• Update existing calendar events
• Delete calendar events

Use cases of Google Calendar MCP Server

• List calendars and view upcoming events within a date range
• Create new events with details like location, description, time zone, and attendees
• Update event titles, times, or other fields
• Delete events using their event ID
• Manage calendars through natural language instructions to Claude

FAQ from Google Calendar MCP Server

What are the prerequisites for using Google Calendar MCP Server?

Node.js 16 or higher, a Google Cloud project with the Calendar API enabled, and OAuth 2.0 credentials (Client ID and Client Secret) set up for a Desktop app type.

How does authentication work?

The server detects missing tokens, starts an authentication server on ports 3000–3004, opens a browser for OAuth login, then saves tokens in .gcp-saved-tokens.json and refreshes them automatically.

What happens if the OAuth token expires?

If the app is in testing mode, the OAuth token expires after 7 days and you must re-authenticate.

Where are authentication tokens stored?

Tokens are stored locally in a file named .gcp-saved-tokens.json in the project root directory.

What if I get an authentication error or port conflict?

Ensure gcp-oauth.keys.json is correctly formatted and placed in the project root. The authentication server tries ports 3000–3004; make sure at least one is available.