Google Workspace now requires a distinct identity for AI agents
From November 11, Google Workspace MCP rejects OAuth clients that are not marked for AI-agent use; ordinary REST-only integrations are unaffected.
If an assistant connects to Gmail, Calendar, Drive or other Workspace services through Google’s MCP servers, check its OAuth client now.
An October 12 developer notice takes effect on November 11: the client must have “Use this client for an AI-powered agent” selected in Google Auth Platform. Unmarked clients are rejected. [1]
Google says clients still unmarked by November 12 remain non-agentic; using MCP afterward requires a new client marked for agent use and an application update. Its notice gives a date, not a closing hour or timezone, so waiting for a presumed end-of-day cutoff would be unwise. [1]
This is not a requirement to rebuild every Workspace integration. REST-only, non-agent applications are unaffected. If the same OAuth client currently supports an agent and ordinary app features, Google directs developers to create a separate client for the agent and keep the existing one for the other features. The relevant MCP services remain in the Developer Preview Program. [1][2]
Take it further
Check the Workspace agent client For developers using Google Workspace MCP. Mark the agent client or create a separate one. Google states November 12 as the transition date without a closing time/timezone; no exact cutoff is assumed.
Sources & details 2 sources
Discuss in your voice app
Take the reporting, visual explanations and original sources into a conversation. Copy the brief, paste it into your preferred assistant, then start its voice mode.
Paste the brief into your voice app to discuss this reporting.October 12 notice begins enforcement on November 11; the source is not redated. Checked 11 November 2026.
Reporting sources
- Google Workspace — developer release notes
Notice effective Nov11: Workspace MCP rejects unmarked OAuth clients; clients unmarked by Nov12 remain non-agentic and a new marked client is required. REST-only integrations unaffected; split shared clients. MCP is Developer Preview. No exact Nov12 timezone provided; do not invent a clock deadline.
- Google Chat — configure the MCP server
Original setup documentation opened; provides developer-preview setup. Release note remains the direct source for effective date and mark-as-agent requirement; no live user configuration tested.
Images & figures
Google Workspace MCP requires an OAuth client marked for an AI-powered agent; ordinary REST-only clients are unaffected.
Euangelion · Source · Usage terms