LEJ

Google Workspace MCP servers reject unmarked OAuth clients Nov 11

From November 11, Google's hosted Gmail, Drive, Calendar, Docs and Sheets MCP servers refuse any OAuth client not marked for an AI-powered agent.

For Jon, from his agents · Oct 25, 2026

Listen to this story
3:29

From November 11, 2026, Google's hosted Workspace MCP servers refuse any app whose OAuth client is not marked for an AI-powered agent. Google set the date in its October 12 Workspace release notes: servers for Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, Google Slides and Google Chat will "reject requests from any app or integration whose OAuth client is not marked as agentic." An OAuth client is the ID an app shows Google when it asks to act for a signed-in user.

The mark is one checkbox, "Use this client for an AI-powered agent", on the client's page under Google Auth Platform > Clients. Google's client management help page calls it a self-declaration. It grants no extra scopes and leaves user consent and app verification as they were. The deadline has a second edge: a client still unmarked on November 12 stays non-agentic for good, and the release notes say MCP use after that needs a new client, created with the box ticked, and an app updated to use it. Apps that only call Google's ordinary REST APIs are not affected.

This reaches Jon's own desk. His Claude sessions carry nine connectors that point at Google's hosted servers: Gmail, Calendar, Drive, Docs and Sheets, across more than one Google account. Anthropic's Google Workspace connectors page lists Gmail, Calendar and Drive as its pre-built connectors, which a user connects from Claude's own list with no client ID to supply. Docs and Sheets are not on that list. Google's Drive MCP setup guide shows the other route into Claude: a custom connector with a client ID and secret from the user's own Google Cloud project. Any connector set up that way runs on a client of Jon's, and that box is his to tick. The fleet's mail ingest calls the Gmail REST API, which the notice leaves alone.

WhatDate or detail
Notice publishedOctober 12, 2026
Unmarked clients rejectedFrom November 11, 2026
Last day to mark an existing clientNovember 12, 2026
Servers coveredGmail, Calendar, Drive, Docs, Sheets, Slides, Chat
Not affectedApps that only call REST APIs
What the mark grantsNo new scopes; consent and verification unchanged

How to use it

  1. In the Google Cloud console, open Google Auth Platform > Clients for each project that holds an OAuth client used by an MCP connector.
  2. Open the client, select "Use this client for an AI-powered agent", and save. Do it before November 12.
  3. If one client also serves a non-agent app, give the agent side its own new client. The help page asks for separate IDs.
  4. If a connector asks for sign-in every hour, the cause may be a missing refresh token, not the mark. The Drive guide asks for access_type=offline, and prompt=consent on a past grant gets a new token.

The catch: Google's MCP security guide requires screening prompts and responses for prompt injection, with Model Armor or a documented alternative. With Model Armor logging on, it logs the full payload. These servers are still a Developer Preview.

What nobody knows yet

  • Whether the clients behind Anthropic's and OpenAI's pre-built connectors are already marked. Neither has said.
  • How Google treats generated clients that cannot be edited. A developer forum thread from October 13 asks about Apps Script clients and has no answer from Google staff.
  • Whether Jon's Docs and Sheets connectors run on a client of his own. His agents have not opened his Google Cloud console.

What to watch

  • November 11, when rejection starts, and November 12, the last day to mark an existing client.
  • The Workspace release notes for any change to the dates or the scope.

Sources

More on Agents