Use Claude with Google Calendar through MCP to inspect schedules, summarize tomorrow’s agenda, and draft safer scheduling suggestions. Copy a working config and understand the OAuth scope before connecting.
Connect Claude to Google Calendar with MCP
If your goal is “ask Claude what is on my calendar, find conflicts, or suggest meeting times without bouncing across tabs,” this is the shortest path.
Recommended MCP servers for this use case
| Server | Best for | Not ideal when | Auth | Permission risk |
|---|---|---|---|---|
| MCP GSuite Server | Calendar reads plus event creation in the same Workspace setup | You only need standalone task management | OAuth2 files + Calendar scopes | High |
| Connect Claude to Google Workspace with MCP | Evaluating Gmail, Calendar, and Tasks together | You already know the workflow is calendar-only | Mixed | High |
Quick selection (30 seconds)
- Pick MCP GSuite if your immediate need is schedule visibility and simple event creation.
- Start with read-heavy prompts such as agenda summaries or conflict checks before allowing event creation.
- Use a lower-risk calendar first if your main calendar includes sensitive customer or executive meetings.
Copy-paste config (Claude Desktop)
{
"mcpServers": {
"mcp-gsuite": {
"command": "uvx",
"args": [
"mcp-gsuite",
"--accounts-file",
"/absolute/path/to/.accounts.json",
"--credentials-dir",
"/absolute/path/to/credentials"
]
}
}
}Keep your .accounts.json metadata descriptive so Claude can distinguish work and personal calendars.
Calendar auth checklist
| Item | Required | Sensitive | Notes |
|---|---|---|---|
| Google Calendar API enabled | Yes | No | Required in Google Cloud before auth |
.gauth.json | Yes | Yes | OAuth client metadata |
.accounts.json | Yes | Yes | Helps separate calendar context across accounts |
| Credentials directory | Yes | Yes | Stores refresh tokens locally |
| Calendar scope | Yes | Yes | Read-only is safer for early rollout if supported by your chosen workflow |
First tool-call prompts
- “What do I have on my agenda tomorrow, and which events are likely conflicts?”
- “Check next week for two-hour meeting slots with Tim and suggest the lowest-conflict options.”
- “Summarize this week’s calendar into deep-work blocks, meetings, and follow-up items.”
Risk and permission notes
- Calendar data can reveal internal project names, customers, travel, and private commitments.
- Suggesting times is lower risk than actually writing events; use read-first rollout where possible.
- Keep work and personal calendars separated in account metadata so Claude does not mix them casually.
FAQ
What is the best Google Calendar MCP option here?
MCP GSuite Server is the best current option in this site because it already supports calendar retrieval and event creation inside the same Workspace setup.
Should I allow Claude to create calendar events immediately?
Not at first. Start with agenda and conflict analysis, then move to proposal workflows, and only then consider event creation.
What is the fastest way to reduce scheduling risk?
Use a lower-risk calendar first and validate read-only prompts before allowing any write-style scheduling actions.
Related pages
- MCP GSuite Server details
- Connect Claude to Google Workspace with MCP
- Connect Claude to Gmail with MCP
Sources and freshness
- Sources: official server pages linked above.
- Updated: March 15, 2026.