Google Calendar MCP Server
Google Calendar MCP Server
Connect Claude to your Google Calendar through the Model Context Protocol.
The Google Calendar MCP Server enables Claude to read events, create meetings, check availability, and manage your schedule using natural language commands.
What Can Claude Do with the Google Calendar MCP Server?
The Google Calendar MCP Server exposes Google Calendar API functionality to Claude through the Model Context Protocol.
Core capabilities:
- Read Events — View upcoming events, meeting details, and schedule information
- Create Events — Schedule new meetings, appointments, and calendar entries
- Check Availability — Find free time slots and check scheduling conflicts
- Update Events — Modify event details, times, or attendees
- Search Calendar — Find specific events by title, date, or attendee
Access scope: Claude can only access calendars and perform operations your OAuth credentials allow. The integration respects Google Calendar sharing and permission settings.
How to Install Google Calendar MCP
Installation requires Google OAuth credentials and Calendar API access.
Prerequisites
Before installing the MCP Server, you need:
- A Google Cloud Platform account
- A project with Google Calendar API enabled
- OAuth 2.0 credentials (Client ID and Client Secret)
For Claude Code
A concrete current path is to use the maintained workspace-mcp Google Workspace server and expose Calendar tools through Claude Code.
export GOOGLE_OAUTH_CLIENT_ID="your-client-id"
export GOOGLE_OAUTH_CLIENT_SECRET="your-client-secret"
claude mcp add google-workspace uvx workspace-mcp --tools calendar
For Claude Desktop
Add the same server to claude_desktop_config.json with your OAuth credentials:
Configuration file locations:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"google_workspace": {
"command": "uvx",
"args": ["workspace-mcp", "--tools", "calendar"],
"env": {
"GOOGLE_OAUTH_CLIENT_ID": "your-client-id",
"GOOGLE_OAUTH_CLIENT_SECRET": "your-client-secret"
}
}
}
}
Restart Claude Desktop after saving the configuration file.
Google OAuth Setup for Calendar MCP
The Google Calendar MCP Server requires OAuth 2.0 authentication.
Setting up OAuth credentials:
- Create a Google Cloud Project
- Go to Google Cloud Console
- Create a new project or select an existing one
- Enable Google Calendar API
- In your project, go to "APIs & Services" → "Library"
- Search for "Google Calendar API"
- Click "Enable"
- Create OAuth 2.0 Credentials
- Go to "APIs & Services" → "Credentials"
- Click "Create Credentials" → "OAuth client ID"
- Choose application type (Desktop app or Web application)
- Configure the OAuth consent screen if prompted
- Download the credentials JSON file
- Configure Required Scopes
The Google Calendar MCP Server requires specific OAuth scopes:
https://www.googleapis.com/auth/calendar.readonly— Read-only access to calendarshttps://www.googleapis.com/auth/calendar.events— Manage calendar eventshttps://www.googleapis.com/auth/calendar— Full calendar access (includes read and write)
Minimum recommended scope: https://www.googleapis.com/auth/calendar.events for reading and creating events.
- Complete OAuth Flow
The MCP Server will initiate an OAuth flow on first use. You'll be redirected to Google to authorize access. Follow the prompts to grant permissions.
OAuth token storage: The MCP Server stores refresh tokens securely for subsequent use. You only need to authorize once unless you revoke access.
Calendar MCP Use Cases & Examples
Example workflows that become possible with the Google Calendar MCP Server.
Check Today's Schedule
Example prompt:
> "Show me all my meetings scheduled for today."
Claude can retrieve your calendar events for the current day.
Create New Meetings
Example prompt:
> "Schedule a team sync meeting tomorrow at 2 PM for 1 hour with john@company.com and sara@company.com."
Claude can create calendar events with specified attendees and times.
Find Available Time
Example prompt:
> "When am I free tomorrow afternoon between 1 PM and 5 PM?"
Claude can check your calendar for free time slots.
Search Past Events
Example prompt:
> "Find all meetings with 'design review' in the title from the last 2 weeks."
Claude can search your calendar history.
Update Existing Events
Example prompt:
> "Move my 3 PM meeting today to 4 PM."
Claude can modify event times and details.
Check Scheduling Conflicts
Example prompt:
> "Do I have any conflicts if I schedule a meeting next Tuesday at 10 AM?"
Claude can check for overlapping events before scheduling.
Note: These are example use cases. Actual capabilities depend on your OAuth permissions and calendar sharing settings.
Google Calendar MCP in Scheduling Operations
Google Calendar MCP is useful when assistants need to read schedules, coordinate meetings, and automate event planning.
What this shows: This screenshot shows the official Calendar API overview, matching real scheduling scenarios like event creation, availability checks, and workflow coordination.
Why this scenario matters: It shows the scheduling layer teams really depend on, making the MCP value clear for meeting coordination, event management, and time-based workflows.
Typical assistant task: Check availability, inspect event details, and coordinate meetings across a live scheduling surface.
Source: Google Calendar API
When to Pick Google Calendar MCP Server vs Microsoft Graph Calendar
This comparison is most useful when both options look plausible on paper but differ in operating model, team fit, and day-to-day workflow cost.
| Decision Lens | This Page's MCP Path | Competitor |
|---|---|---|
| Best For | Teams coordinating schedules inside Google Workspace calendars and assistant-led event workflows. | Organizations where Microsoft 365 calendars are the operational source of truth. |
| Where MCP Wins | Google Calendar MCP wins when availability, events, and scheduling automation all live in the Google ecosystem. | |
| Tradeoff to Watch | It is a weaker fit for organizations that already depend on Graph calendar objects and Outlook-native workflows. | |
| Choose This Path When | Choose Google Calendar MCP for Workspace scheduling; choose Graph Calendar for Microsoft 365-centered teams. | |
| Sources | ||
Frequently Asked Questions
Is the Google Calendar MCP Server free?
Do I need a Google Workspace account?
What permissions does Claude need?
Can Claude access other people's calendars?
How do I revoke access?
Does it work with multiple calendars?
What if I get OAuth errors?
Use Google Calendar MCP in Verdent
Verdent provides streamlined Google Calendar integration with simplified OAuth setup. This is Verdent's platform-level integration flow, not the default setup path from Google's official documentation.
Connect your Google account once and access calendar operations across all Verdent projects without manual OAuth configuration.