⇄ Workspace MCP agentic
● Local only

Mark agentic OAuth before MCP locks you out

Nov 11 reject · Nov 12 lock-in · Apps Script must self-build · split human vs agent. Export a local checklist.

Your situation Input

1. Do you connect Google Workspace via MCP?


Path card Output

Answer the prompts on the left to get a path card.


    

Editable client

Console checkbox path before Nov 11 — mark “Use this client for an AI-powered agent”.

Apps Script

Default OAuth client usually cannot toggle agentic — self-build a Cloud client.

Split traffic

Separate human vs agent clients so admins can tell traffic apart after lock-in.

Local

Answers stay in the browser. No Google login on this site.

Deadlines

2026-11-11 reject unmarked MCP clients · 2026-11-12 permanent non-agentic lock-in.

REST note

Workspace REST-without-MCP is not the focus — do not let that drown the MCP checklist.