Skip to content
Status

MCP setup guides / Google Calendar (Speakeasy-hosted)

Google Calendar (Speakeasy-hosted)

Connect the Speakeasy-hosted Google Calendar MCP server with a Google OAuth client, so each person can list calendars, read and manage events, and check availability as themselves.

Speakeasy hosts an MCP server for Google Calendar at https://catalog.speakeasy.com/calendar/mcp. It calls the standard Google Calendar API with each person’s own OAuth token, so agents can list calendars, read and manage events, and check availability with exactly the access that person already has in Google Workspace.

Why use this guide

Use this guide to connect Google Calendar without applying to the Google Workspace Developer Preview. Google’s own Calendar MCP server is available only to projects accepted into that program, and it also needs an MCP API service and the MCP Tool User role. This Speakeasy-maintained server needs none of these. Organizations already in the preview that prefer Google’s server can follow the Google Calendar guide instead.

This guide creates a Google OAuth client for the server and adds the server to a Speakeasy project. To set up Gmail, Google Calendar, and Google Drive together with one shared client, follow Google Workspace setup instead.

Prerequisites

Section titled “Prerequisites”
  • A Google Workspace account in the organization whose users will connect.
  • A Google Cloud project owned by that organization, and permission to enable APIs (Service Usage Admin or Owner) and configure Google Auth Platform.
  • If the Workspace restricts third-party access to Google Calendar, a Workspace administrator with the Service Settings privilege.
  • The mcp:write scope in the Speakeasy project, held by the default Admin role.

Enable the Google Calendar API

Section titled “Enable the Google Calendar API”

Open the Google Cloud console and select the project in the toolbar’s resource selector. Keep it selected for every Google Cloud step.

Go to APIs & Services > API Library, search for Google Calendar API, and click “Enable”.

Section titled “Configure the consent screen”

The consent screen is what people see when they first connect the server. Configure it under Google Auth Platform:

  • Branding: open Google Auth Platform > Branding and click “Get Started” if prompted. Enter an app name people will recognize, such as Speakeasy Google Calendar, and a monitored User support email.
  • Audience: choose Internal. Only users in the organization can connect, and Google app verification does not apply. The option appears only when the Cloud project belongs to the Workspace organization.
  • Contact information: enter a monitored email address.
  • Finish: with approval from the application or security owner, accept the Google API Services: User Data Policy, then click “Create”.

External audiences

With an External audience, the app starts in testing, only listed test users can connect, and Google may require app verification before it is published. Use Internal unless people outside the Workspace organization need to connect.

Next, open Data Access and click “Add or Remove Scopes”. Under Manually add scopes, paste these five scopes. Click “Add to Table”, then “Update”, then “Save”.

https://www.googleapis.com/auth/calendar.calendarlist.readonly
https://www.googleapis.com/auth/calendar.events.readonly
https://www.googleapis.com/auth/calendar.events
https://www.googleapis.com/auth/calendar.freebusy
https://www.googleapis.com/auth/calendar.settings.readonly

Create the OAuth client

Section titled “Create the OAuth client”

Go to Google Auth Platform > Clients and click “Create Client”. Set Application type to Web application and give the client a name, such as Speakeasy AI Control Plane.

Under Authorized redirect URIs, click ”+ Add URI” and enter the Speakeasy callback URL, then click “Create”:

https://ai.speakeasy.com/mcp/remote_login_callback

If the organization serves MCP servers from a custom domain, register the callback URI shown in the Speakeasy authorization server sheet instead.

Copy the Client ID and Client Secret into an approved secret store before closing the dialog.

The secret is shown once

Google does not show the client secret again after the dialog closes. If it closes before the secret is stored, create a new web client with the same redirect URI and use its credentials instead.

Permit the app under Workspace policy

Section titled “Permit the app under Workspace policy”

Skip this step only after the Workspace security owner confirms that Google Calendar is not Restricted for third-party apps.

  • In the Google Admin console, go to Security > Access and data control > API controls > Manage App Access.
  • Under Configured apps, click “Configure new app”, search for the Client ID, and select the matching app.
  • Choose the organizational units that contain the connecting users, set Access to Google data to Trusted, and click “Finish”.

Add the server in Speakeasy

Section titled “Add the server in Speakeasy”
  • In the sidebar under MCP Gateway, select MCP, then Add new, then Hosted remotely.
  • Enter the server URL below and click “Verify connectivity”.
  • Under Identity, choose User Identity. Confirm the authorization server is Google (https://accounts.google.com/), then choose Manual.
  • Paste the Client ID and Client secret from the OAuth client. Google requires the secret even though the field is labeled optional.
  • Leave Advanced > Scope empty, since the server requests its own scopes, and click “Save”.
https://catalog.speakeasy.com/calendar/mcp

If the server shows Disabled after saving, open its Settings > Danger Zone > Server Availability and turn on Enable MCP server.

Connect and test

Section titled “Connect and test”

Connect an MCP client to the server, or add the server to a gateway endpoint. On first use, each person signs in with their Google account and approves the requested access.

Ask the agent to list tomorrow’s events. Each call runs as the signed-in person and returns only data that person can already access.

Next steps

Section titled “Next steps”