Skip to main content
Google hosts official remote MCP servers for Workspace. Gmail, Drive, and Calendar are each a separate connector, and you connect them with your own Google OAuth app so the Hub talks to Google directly under your account.
This guide is for Google Workspace accounts (your organization’s Google). In Google Auth Platform, set the user type to Internal — an internal app only your organization can use, which skips Google’s app-verification review entirely.
Do not leave an External app in Testing. An External app left in Testing silently expires sign-in after 7 days.

Connector URLs

Add each service you want as its own connector, using these URLs: You can use the same Client ID and Secret for all of them. There is no catalogue id gcp; that is the id of this guide in the CLI (vio docs connectors gcp).

Create the OAuth app

1

Create a Google Cloud project

In the Google Cloud console, create a project (or reuse one) inside your Workspace organization.
2

Enable the Workspace MCP APIs

Under APIs & Services → Library, enable the APIs for the services you want: gmailmcp.googleapis.com, drivemcp.googleapis.com, calendarmcp.googleapis.com, and chatmcp.googleapis.com. Contacts uses people.googleapis.com.
3

Set Google Auth Platform to Internal

Open Google Auth Platform and choose Internal as the user type. Fill in the basic app details. Internal is available only inside a Workspace organization.An External app left in Testing silently expires sign-in after 7 days. Publishing an External app, or switching it to Internal, is what avoids that.
4

Create an OAuth client

Create an OAuth client ID (Web application). Add this exact URL to Authorized redirect URIs:
That is the production redirect. vio connect prints the URL it will actually send, under “Add this exact URL to the provider’s Authorized redirect URIs:”. The printed line matches the URL above unless this machine’s control_url is overridden. The Hub shows the same URL as Copy callback URL. Save, then copy the Client ID and Client Secret.

Connect in the Hub

1

Add the connector

Add a connector using the URL for the service you want (Gmail, Drive, or Calendar).
2

Paste your credentials

Enter your Client ID and Client Secret in the connector’s settings, then click Connect.
3

Approve access

Your browser opens Google’s consent screen. Approve it, and the connector’s tools load. Repeat for each service you added.
Add each service as its own connector, reusing the same Client ID and Secret. Each shows up with its own tools.

Scopes

When a bundle does not declare requires[].scopes for that connector, vio connect asks for these. A non-empty requires[].scopes, or --scopes, replaces the default for that connect.

From the CLI

Add the same pair to .vio/.env.connectors, then run vio connect. Leave the secret out of agent.vio.
vio docs connectors gcp prints this guide. The catalogue ids gmail, google-drive, google-calendar, google-chat, and google-contacts print it too. vio connectors <id> and the vio connect prompt point here when the connector needs this app. For the general flow and where the Hub stores your Client Secret, see Bring your own OAuth app.