LABSCO SUMMARY
Your agent books and checks meetings in Google Calendar.
Scheduling is its strong suit: it suggests times that work across several people's calendars, then books the event with attendees and a Google Meet link.
What it is
A remote MCP server Google runs at calendarmcp.googleapis.com. It acts with your Google account's own permissions. It is part of the Google Workspace Developer Preview Program, which gives early access to features.
What you get
- Your calendar list, so you can say 'my family calendar' instead of an ID
- Events listed by calendar and time, or one event in full
- Your primary calendar searched by topic or keyword
- Suggested meeting times across one or more people's calendars
- Events created, updated or deleted, with attendees and a Google Meet link
- Replies to invitations: accepted, declined or tentative
Requirements
- A Google account in the Google Workspace Developer Preview Program, and a Google Cloud project with the Calendar API and the Calendar MCP service turned on.
- You set up an OAuth consent screen and create your own OAuth client ID and secret in that project, then enter them in your MCP client.
- In Claude.ai or Claude Desktop this is a custom connector, which needs a Pro, Max, Team or Enterprise plan.
- Google's guide adds only read-only Calendar scopes to the consent screen; add the calendar.events scope if you want it to create or change events.
- Google warns that event text from strangers can carry hidden instructions, so review what your agent does on your behalf.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen