Google Calendar MCP exposes calendars and events that the authorized Workspace user can access. It uses Google OAuth 2.0 only, after the Workspace Developer Preview and required Google APIs are enabled.
This guide covers the Google-side preparation for the Google Calendar remote MCP server. It applies to any compatible MCP client. The Google Calendar agent template is separate from this Cloud-project and OAuth setup.
Google Calendar MCP is part of the Google Workspace Developer Preview Program. Its Streamable HTTP endpoint is https://calendarmcp.googleapis.com/mcp/v1 and it authenticates with OAuth 2.0.
Choose a connection method
Google Workspace MCP supports Google OAuth 2.0 for Calendar; it does not offer a bearer-token alternative for this server. The Google Workspace MCP configuration guide is the source of truth for the endpoint, enabled APIs, OAuth client requirements, and supported scopes.
Recommended: Google OAuth for Workspace MCP
Complete the following vendor-side setup before connecting the MCP server.
- Join the Google Workspace Developer Preview Program.
- Create a dedicated Google Cloud project, separate from unrelated production integrations.
- Prepare a test Calendar account with a few non-production events.
- Use an Internal consent screen for a single Workspace organization. For an External app that remains in testing, add the test identity under Google Auth Platform → Audience → Test users.
- Select this project, then click Enable on both services: Google Calendar API (
calendar-json.googleapis.com) and Google Calendar MCP API (calendarmcp.googleapis.com). The Calendar API alone does not enable the MCP service.
Configure OAuth for an AI agent
In Google Auth Platform, complete the Branding and Audience settings. In Data Access, start with only these read scopes:
https://www.googleapis.com/auth/calendar.calendarlist.readonlyhttps://www.googleapis.com/auth/calendar.events.freebusyhttps://www.googleapis.com/auth/calendar.events.readonlyCreate a Web application OAuth client under Clients using Google Auth Platform → Clients → Create client. Add Dome's exact callback URL:
https://api.domesystems.ai/oauth/callbackSelect Use this client for an AI-powered agent. Google requires that option for user-delegated OAuth clients that call Workspace MCP servers. Store the resulting client ID and secret in a secret manager; do not add event-write, RSVP, calendar-edit, or delete scopes to a read-only setup.
If your client supports custom authorization parameters, use access_type=offline for a refresh token. Use prompt=consent when a previously authorized test user needs a fresh refresh token.
Verify Calendar MCP
Use this checklist to confirm the MCP server is connected with the intended access.
- Connect to
https://calendarmcp.googleapis.com/mcp/v1with the new OAuth client. - Complete consent as the test Calendar identity.
- Confirm that Calendar MCP tools are discovered.
- List a known test calendar, query free/busy time, and read a known event.
- Confirm that event creation, updates, cancellation, and RSVP actions are unavailable.
Google's Workspace MCP configuration guide is the authority for enabled APIs, endpoint, OAuth behavior, and current scopes. Revisit it when Google changes the Developer Preview contract.
Troubleshooting
If the setup does not work as expected, check these common causes.
- If Google rejects authorization, re-check the Developer Preview enrollment, client type, AI-agent setting, exact redirect URI, test-user access, and requested scopes.
- If authorization succeeds but no Calendar MCP tools appear, confirm that both the Google Calendar API and Google Calendar MCP API are enabled in the Cloud project that owns the OAuth client.
- If the expected calendar or event is unavailable, verify the test identity's Calendar sharing and scope before widening access.
Next steps
Deploy the Google Calendar agent template to create a governed agent in Dome that can work with the authorized calendars and events, with the template's included model, tools, and rules.
