Antigravity doesn't support MCP OAuth specifications

Paste your error / 粘贴报错原文

Paste an error to match it against the wiki. / 粘贴报错后自动匹配。

Error text / 报错原文

Antigravity doesn't support MCP OAuth specifications
client ID and secret
agent identity

What it means

Google Cloud documents a current Antigravity limitation: some remote MCP OAuth flows cannot authenticate because the client cannot provide the required client identity.

Most common causes

Remote MCP server requires OAuth client ID and secret
Agent identity is mandatory for the server
Tools are visible but calls fail authorization
The client supports discovery but not the needed credential exchange

Fastest fix

Use a supported client for that MCP server
Switch to a local MCP wrapper with environment credentials
Use a service account where supported
Check whether the server offers a non-OAuth local transport

Safe fix

Use least-privilege service accounts for cloud MCP tools
Separate personal identity from agent identity
Document which clients support each MCP auth mode
Avoid broad OAuth scopes for agent tools

What not to do

Do not fake client secrets in public config
Do not hardcode personal refresh tokens
Do not assume visible tools mean authenticated tools

How to confirm the fix

Run the smallest reproducible command first, then retry the agent task only after authentication, quota, and tool discovery are stable.

echo $GOOGLE_APPLICATION_CREDENTIALS
gcloud auth application-default print-access-token
node --version