MCP server
Google Calendar
Let an AI client read or change a test calendar without exposing real attendees, links, or protected locations.
Published by the company that makes the product.
What it can access
OAuth can expose event titles, attendees, links, locations, and notes, and can permit writes.
Security note
Developer Preview. Connect a test calendar only. Never let a first trial send invitations or expose protected meeting locations.
Do you need it?
Connect only for a repeated scheduling workflow. Adding one deadline manually is safer and faster.
Capability and permissions
Calendar access can expose event titles, attendees, meeting links, locations, and notes. Write access can create, update, or cancel events and may notify people.
Least-privilege setup
As of 2026-09-01, Google’s Workspace MCP servers are Developer Preview. Create a separate test calendar with no subscribers. Connect a workshop account and leave real organisational calendars unshared.
Harmless success test
Create an invented event with no guests. Ask the client to move it by ten minutes. Confirm no invitation or email was sent.
Disable, revoke, remove
Disconnect in the AI client, revoke Google Account access, remove the workshop account from the test calendar, and delete the event and calendar.
When not to connect
Do not connect calendars that reveal protected meetings, travel, legal appointments, source identities, or participant locations.