Google Workspace MCP Servers

Aembit supports the official Google Workspace MCP servers, which let AI agentsAI Agent: A software workload that authenticates to systems, requests credentials, and accesses resources, either on behalf of a person or on its own. Aembit secures AI agents with the same identity-first model it uses for any workload. User-driven agents such as Claude Desktop also carry a blended identity that ties access to both the user and the agent.Learn more read Drive files, calendar events, and contacts through MCPModel Context Protocol: A standard protocol for AI agent and server interactions that defines how AI assistants communicate with external tools and data sources.Learn more(opens in new tab) tools.

This page describes how to configure three Google Workspace MCP serversMCP Server: A server that implements the Model Context Protocol to provide tools, resources, or data to AI agents and MCP clients.Learn more(opens in new tab): Google Drive, Calendar, and People. The Aembit MCP Identity GatewayMCP Identity Gateway: A component that brokers MCP traffic between MCP clients and target MCP servers, validating authorization and presenting Aembit-managed credentials on each request.Learn more brokers the connection. Each user authenticates with their own Google identity, and the Gateway injects their token into MCP requests.

This guide builds the Gateway-to-Server PolicyGateway-to-Server Policy: The Access Policy that authorizes the MCP Identity Gateway to access an MCP server on behalf of authenticated users—the Gateway itself is the Client Workload. Also called right-side auth; each MCP server behind the Gateway needs its own.Learn more—the second of the two Access PoliciesAccess Policy: Access Policies define, enforce, and audit access between Client and Server Workloads by cryptographically verifying workload identity and contextual factors rather than relying on static secrets.Learn more the MCP Identity Gateway requires. You create the first, the Client-to-Gateway PolicyClient-to-Gateway Policy: The Access Policy that validates which MCP client can connect to the MCP Identity Gateway and authenticates users through your Identity Provider. Also called left-side auth; you create one per MCP client and Gateway combination.Learn more, during Gateway setup.

Looking for direct Google API access?

This page covers MCP tool access through Aembit’s MCP Identity Gateway. To broker credentials for a Google REST API as a traditional Server WorkloadServer Workload: Server Workloads represent target services, APIs, databases, or applications that receive and respond to access requests from Client Workloads.Learn more, see the Server Workload guides instead.

Prerequisites

Before you begin, ensure you have the following:

• A Google Cloud project where you can enable APIs and create OAuth credentials
• A Google Workspace organization enrolled in Google’s Developer Preview Program (see Requirements and considerations)
• A configured Aembit MCP Identity Gateway

Requirements and considerations

Before you configure Google Workspace, review these requirements and behaviors specific to Google’s MCP servers.

• Enroll in Google’s Developer Preview Program. Google’s Workspace MCP servers are available only through the Developer Preview Program. Until your organization enrolls, Google returns permission errors for every tool call. Preview enrollment also expands the data Google collects on the vendor side. Review Google’s Preview terms before you enroll.
• Configure each service on its own. Drive, Calendar, and People each require their own GCP OAuth client, their own enabled API, and their own Aembit Credential Provider, Server Workload, and Access Policy.
• The People server uses a non-standard host. Unlike Drive and Calendar, Google hosts the People MCP server directly at people.googleapis.com, not on a dedicated *mcp.googleapis.com subdomain.
• Google Chat isn’t available. The Gateway returns an “Internal error encountered” for every Google Chat tool, so this guide doesn’t cover Chat.
• Gmail isn’t available. This guide doesn’t cover Gmail.

Service settings

Each service uses the same configuration flow but different values. Use the values for the service you’re configuring in the following steps. For Drive and Calendar, the scopes grant read and write access. Substitute the .readonly variant (for example, https://www.googleapis.com/auth/drive.readonly instead of drive) if your agents only need to read data.

Drive

Setting	Value
OAuth scope	https://www.googleapis.com/auth/drive
MCP Server URL	https://drivemcp.googleapis.com/mcp/v1
Server Workload host	drivemcp.googleapis.com
URL Path	/mcp/v1

Calendar

Setting	Value
OAuth scope	https://www.googleapis.com/auth/calendar
MCP Server URL	https://calendarmcp.googleapis.com/mcp/v1
Server Workload host	calendarmcp.googleapis.com
URL Path	/mcp/v1

People

Setting	Value
OAuth scope	https://www.googleapis.com/auth/contacts.readonly https://www.googleapis.com/auth/directory.readonly https://www.googleapis.com/auth/userinfo.profile
MCP Server URL	https://people.googleapis.com/mcp/v1
Server Workload host	people.googleapis.com
URL Path	/mcp/v1

Set up your Google Cloud Platform project

Repeat this section for each Google Workspace service you want to enable. Each service needs its own enabled API and its own OAuth client.

Drive

Google doesn’t support OAuth Dynamic Client Registration, so an administrator must create a GCP OAuth 2.0 client before users can authenticate.

1. Enable the Drive API on your GCP project: gcloud services enable drive.googleapis.com --project=<YOUR_PROJECT>
2. In the GCP Console, go to APIs & Services > OAuth consent screen. Choose Internal for same-org users, or External for cross-org testing. Under Scopes, add https://www.googleapis.com/auth/drive. For read-only access, use https://www.googleapis.com/auth/drive.readonly instead.
3. Go to APIs & Services > Credentials, click Create Credentials > OAuth 2.0 Client ID, and select Web application as the application type. Give it any name. You add the Aembit Callback URL under Authorized redirect URIs after you create the Credential Provider.
4. Copy the Client ID and Client Secret, and store them for the Credential Provider configuration.

Calendar

Google doesn’t support OAuth Dynamic Client Registration, so an administrator must create a GCP OAuth 2.0 client before users can authenticate.

1. Enable the Calendar API on your GCP project: gcloud services enable calendar-json.googleapis.com --project=<YOUR_PROJECT>
2. In the GCP Console, go to APIs & Services > OAuth consent screen. Choose Internal for same-org users, or External for cross-org testing. Under Scopes, add https://www.googleapis.com/auth/calendar. For read-only access, use https://www.googleapis.com/auth/calendar.readonly instead.
3. Go to APIs & Services > Credentials, click Create Credentials > OAuth 2.0 Client ID, and select Web application as the application type. Give it any name. You add the Aembit Callback URL under Authorized redirect URIs after you create the Credential Provider.
4. Copy the Client ID and Client Secret, and store them for the Credential Provider configuration.

People

Google doesn’t support OAuth Dynamic Client Registration, so an administrator must create a GCP OAuth 2.0 client before users can authenticate.

1. Enable the People API on your GCP project: gcloud services enable people.googleapis.com --project=<YOUR_PROJECT>
2. In the GCP Console, go to APIs & Services > OAuth consent screen. Choose Internal for same-org users, or External for cross-org testing. Under Scopes, add the three scopes this server uses: contacts.readonly (the user’s personal contacts), directory.readonly (the Workspace directory of all users in the organization), and userinfo.profile (the authenticated user’s own profile).
3. Go to APIs & Services > Credentials, click Create Credentials > OAuth 2.0 Client ID, and select Web application as the application type. Give it any name. You add the Aembit Callback URL under Authorized redirect URIs after you create the Credential Provider.
4. Copy the Client ID and Client Secret, and store them for the Credential Provider configuration.

Configure the Credential Provider

Create an MCP User-Based Access Token Credential ProviderCredential Provider: Credential Providers obtain the specific access credentials—such as API keys, OAuth tokens, or temporary cloud credentials—that Client Workloads need to authenticate to Server Workloads.Learn more in Aembit for the service.

1. Log into your Aembit Tenant.

2. Go to Credential Providers in the left sidebar and click + New.

3. Configure the following fields:

   Field	Value
   Name	A user-friendly name
   Credential Type	MCP User-Based Access Token
   MCP Server URL	Your service’s MCP Server URL (see Service settings)
   Client ID	The Client ID you copied from Google Cloud
   Client Secret	The Client Secret you copied from Google Cloud
   Scopes	Your service’s OAuth scope (see Service settings)
   PKCE Required	On

   For MCP Server URL, click Discover to populate the Authorization URL and Token URL.

4. Click Save.

5. Copy the read-only Callback URL from the Credential Provider.

Finish configuring the OAuth client

Drive

After you create the Credential Provider, copy its read-only Callback URL and return to the GCP OAuth 2.0 Client ID you created in APIs & Services > Credentials.

1. Open the OAuth 2.0 Client ID, and under Authorized redirect URIs click Add URI, paste the Aembit Callback URL, then click Save.
2. Confirm the Credential Provider scope matches the scope you added on the OAuth consent screen: https://www.googleapis.com/auth/drive

Calendar

After you create the Credential Provider, copy its read-only Callback URL and return to the GCP OAuth 2.0 Client ID you created in APIs & Services > Credentials.

1. Open the OAuth 2.0 Client ID, and under Authorized redirect URIs click Add URI, paste the Aembit Callback URL, then click Save.
2. Confirm the Credential Provider scope matches the scope you added on the OAuth consent screen: https://www.googleapis.com/auth/calendar

People

After you create the Credential Provider, copy its read-only Callback URL and return to the GCP OAuth 2.0 Client ID you created in APIs & Services > Credentials.

1. Open the OAuth 2.0 Client ID, and under Authorized redirect URIs click Add URI, paste the Aembit Callback URL, then click Save.
2. Confirm the Credential Provider scopes match the scopes you added on the OAuth consent screen: https://www.googleapis.com/auth/contacts.readonly https://www.googleapis.com/auth/directory.readonly https://www.googleapis.com/auth/userinfo.profile

Authorize the Credential Provider

1. Return to the Credential Provider in Aembit and click Authorize.

2. Choose your Google Account and approve access. The Credential Provider status changes to Ready when the flow completes.

Create the Server Workload

1. Go to Server Workloads in the left sidebar and click + New.

2. Configure the following fields:

   Field	Value
   Name	A user-friendly name
   Host	Your service’s Server Workload host (see Service settings)
   Application Protocol	MCP
   Port	443 with TLS
   URL Path	Your service’s URL Path (see Service settings)
   Authentication method	HTTP Authentication
   Authentication scheme	Bearer

3. Click Save.

Create an Access Policy

This section creates the Gateway-to-Server Access Policy, which authorizes the MCP Identity Gateway to access each Google Workspace service on behalf of authenticated users.

Create an Access Policy linking the MCP Identity Gateway (as the Client WorkloadClient Workload: Client Workloads represent software applications, scripts, or automated processes that initiate access requests to Server Workloads, operating autonomously without direct user interaction.Learn more), the Credential Provider you created, and the Server Workload for each Google Workspace service.

The Gateway is the Client Workload

In this policy, the Client Workload is the MCP Identity Gateway itself—not the AI agent or individual users. The AI agent connects through the separate Client-to-Gateway policy, and the Credential Provider enforces per-user access.

For step-by-step instructions, including the Client Workload settings that identify the Gateway, see Create the gateway-to-server Access Policy.

Verify

After a user authorizes access, the Aembit AI Access Authorized page lists each configured Google Workspace MCP Server as Ready. The AI agent can then call the corresponding MCP tools (such as listing Drive files or calendar events) through the Gateway.