AI News(Updated )

Google Workspace MCP OAuth: November 2026 Policy and Client Migration

Google announced a November 11, 2026 start date for rejecting certain Workspace remote MCP requests. Its October 12 release notes specify that user-delegated OAuth 2.0 clients calling Google’s remote Workspace MCP servers need the Use this client for an AI-powered agent setting. The notice also warned that clients left unmarked by November 12 would remain non-agentic and require a new agent-marked client for MCP use.

This is a published enforcement schedule, not a failure rate we measured. Google’s current MCP troubleshooting guide adds an important operational distinction: update an existing client when that setting remains editable; create a new agentic client when it cannot be updated or when the original client also serves non-agent features. Developers should follow the behavior actually available in their own authorized Cloud project rather than assuming every existing ID must always be replaced.

This is an authentication change for a defined protocol and client type, not a shutdown of ordinary Gmail, Google Drive or Google Calendar REST API integrations. A tool’s name, or the mere fact that an app uses an AI model, does not establish that the requirement applies.

The timeline comes from Google Workspace’s October 12 release notes; the official remote MCP configuration guide describes the client setting and exceptions.

1. The rule and the dates

Google Auth Platform > Clients includes a checkbox labeled Use this client for an AI-powered agent. Google requires it for relevant user-delegated OAuth clients calling Workspace remote MCP servers.

  • October 12, 2026: Google documented the new OAuth client requirement for multiple Workspace remote MCP servers. The current configuration guide lists the supported Workspace product-specific MCP services separately.
  • November 11, 2026: The release notes scheduled rejection of requests from unmarked OAuth clients that call the specified Workspace MCP servers. This article has not independently measured server-side enforcement.
  • November 12, 2026: The release notice says existing clients still unmarked by this date remain non-agentic and may need replacement. The current setup/troubleshooting guide separately documents updating an existing client if the option is still available. Where it cannot be changed, create a new agent-marked client and update the affected app.

These documents should be read together. The dated release notice sets out Google’s transition policy; the current troubleshooting guide describes the supported response to the individual client’s actual settings. Neither is evidence that an ordinary REST API integration has failed.

The notice does not give a specific global cutoff hour or time zone. Do not invent a 9:00 a.m. or midnight local deadline from the date alone.

Services have different rollout and Developer Preview eligibility conditions. This article concerns Google’s own remote Workspace MCP servers, not every third-party MCP implementation that happens to access Google data through different APIs.

2. Which integrations need attention?

A. A coding or business agent calls Gmail, Drive, Docs, Sheets, Slides, Calendar or Chat using Google’s remote MCP endpoint and a user-delegated OAuth client.

This is the main affected case. Identify the exact client ID used to obtain the user-delegated token. If the client is unmarked and can no longer be changed, follow Google’s instructions to create a new agent-marked client and update the MCP configuration.

B. An application calls ordinary Workspace REST APIs, without Google’s remote MCP server.

Google says non-agentic REST-only apps are not affected by this change. An existing REST integration does not become noncompliant simply because a different product uses MCP or because the app supports an AI feature elsewhere.

C. A single OAuth client powers both agent/MCP and ordinary app workflows.

Google recommends separate OAuth client IDs: preserve the existing standard client for normal application features, and make a dedicated agentic client for the MCP workflow. This separates monitoring and policy from traditional user interactions.

D. A service account uses domain-wide delegation.

A delegated service account is not managed through Google Auth Platform’s normal user OAuth clients, so it cannot select that checkbox. Google’s remote MCP guide explicitly says those requests are not rejected solely for lacking the agent setting. Access still depends on the Workspace administrator’s domain-wide-delegation configuration, and sensitive actions can require human confirmation.

E. Google Apps Script calls Google’s remote Workspace MCP endpoint.

The Apps Script-managed default OAuth client cannot be marked as agentic. Google describes using a separate agentic OAuth client, the OAuth2 for Apps Script library, and the resulting access token instead of the token from ScriptApp.getOAuthToken. Apps Script code that does not call Workspace MCP is unaffected by the new checkbox requirement.

These differences matter more than a blanket headline about “all Google AI integrations breaking.”

3. Check an affected OAuth client safely

Only authorized project administrators should change OAuth client configuration. A useful inspection and recovery order is:

  1. Confirm the protocol. Is your app calling Google’s remote MCP endpoint, or a standard REST API? Do not infer the route from a product name.
  2. Identify the actual OAuth client ID used for the remote MCP call. Several apps may access the same user’s account through different clients.
  3. In the owning Cloud project, open Google Auth Platform > Clients and inspect Use this client for an AI-powered agent.
  4. If Google Auth Platform still lets you mark the existing client for agent use, follow the current Google Workspace troubleshooting instructions for that client. If the setting cannot be changed, create a new agent-marked client and update your MCP application. Do not assume a date alone tells you which option your particular client supports.
  5. If the current client also powers non-agent features, preserve it and migrate just the MCP workflow to a separate agentic client.
  6. Update the target MCP client’s authorized redirect URI, configuration and OAuth consent flow as appropriate. Never publish the OAuth client secret, refresh token or user access token.
  7. Perform one harmless, approved tool query and inspect the actual authentication result. A successful interactive sign-in is not proof that a remote MCP server accepted the later tool call.

Google Cloud’s OAuth client management guide explicitly says that tagging an OAuth client does not grant additional scopes or privileges to access user data. Standard user consent and OAuth application verification still apply. An agentic label is not authorization to read someone else’s account or bypass Workspace administrator controls.

4. Why might a connector still fail after migration?

Different failures need different remedies.

Wrong client ID or missing agent designation

If the remote MCP request is rejected, first check the actual user-delegated OAuth client, not only the project name. An app may still use cached or older client configuration. The official troubleshooting steps distinguish an existing client that can be updated from one that must be replaced.

A developer who administers several clients should not rotate all of them reflexively. Changing a shared client can disrupt unrelated users and services.

Hourly reauthentication without a refresh token

Google separately documents that a refresh token requires the OAuth authorization parameter access_type=offline; the OpenID Connect scope offline_access alone does not accomplish the same thing for Google’s OAuth flow. When appropriate, an authorized client can use prompt=consent to obtain a new refresh token for an already-authorized user.

This addresses repeated sign-in prompts, not the agentic checkbox. Do not mistake one for the other.

Service account or Apps Script exception

As above, domain-wide-delegated service accounts have their own administration rules, while Apps Script’s managed OAuth client cannot be marked and needs a separate OAuth client for remote MCP access. Neither exception means every request is permitted.

Local MCP server errors

A local Python MCP server using STDIO can fail because of a broken interpreter path, protocol framing or package version. That is a different path from Google’s remote Workspace MCP user OAuth restriction. Our Python MCP SDK server guide explains the local process boundary, not this new Google policy.

Developer Preview and tool authorization

Many Google Workspace MCP endpoints remain subject to product-specific availability, developer preview requirements, user consent, administrative policy and confirmation of sensitive tool actions. A valid agent-marked OAuth client is necessary in the affected flow, but not sufficient for every endpoint or operation.

5. The engineering lesson: identity and permissions are separate layers

The OAuth client ID identifies the application requesting access. User consent, OAuth scopes, project verification and Workspace administration decide the actions the application can perform. Marking a client as agentic adds a separate policy signal for AI-mediated workflows.

For teams maintaining several tools, an inventory should record the app owner, protocol, Cloud project, OAuth client class, endpoint, responsible administrator and agent-designation status. It should not contain raw client secrets or refresh tokens.

A successful MCP tool call also does not mean the overall agent task completed safely. Our MCP test evidence audit explains the limits of treating tool responses or passing tests as proof of the final repository state.

Separate an authentication fix from a safety guarantee. An agent can have valid OAuth credentials while still lacking proper restrictions on what it may do with tools.

6. What we can and cannot conclude

Google’s public documents establish the announced schedule, OAuth client setting and specific exceptions. They do not independently show which private customer integrations actually experienced rejected requests after the stated start date. No live Workspace MCP rejection, third-party connector failure or customer credential migration was reproduced for this article.

It would therefore be misleading to claim that every ChatGPT connector, every Google Workspace automation or every Apps Script integration failed on November 11.

The change is specific enough for developers to act on immediately: determine whether your integration uses the Google-hosted Workspace remote MCP server with user-delegated OAuth, check the correct client, and migrate only if the documented rule applies.

Primary sources

Editorial note: Originally published November 12, 2026; corrected November 12, 2026 to distinguish Google’s announced enforcement schedule from observed failures, and to reconcile the dated release note with the current existing-client troubleshooting guidance. No production OAuth migration or third-party connector failure was measured for this analysis.

BC

Written by B. Cho

Systems & AI Infrastructure Engineer

Specializing in GPU inference engines (vLLM, SGLang, Ollama), CUDA memory allocation, and Model Context Protocol (MCP) infrastructure on Linux workstations.