Environment: Claude Managed Agents, Anthropic Python/Node SDK, vault credentials API
Date observed: 2026-05-27
SUMMARY
When creating MCP credentials for Google Drive, Gmail, and Calendar via vaults.credentials.create, the API rewrites the mcp_server_url I submitted to a different URL server-side. The rewritten URL points to a backend that returns "This MCP server has been turned down" at tool-call time. mcp_server_url is documented as immutable after creation, so we cannot patch existing credentials.
REPRO
Using the official @anthropic-ai/sdk Node client (latest), authenticated as admin:
await client.vaults.credentials.create({
vault_id: ,
name: "google-drive",
mcp_server_url: "https://drivemcp.googleapis.com/mcp/v1",
oauth_token: { access_token: "", refresh_token: "" }
});
Then vaults.credentials.retrieve() returns mcp_server_url = "https://api.anthropic.com/mcp/gdrive/mcp", not the URL we sent.
OBSERVED REWRITES (sent → stored)
https://drivemcp.googleapis.com/mcp/v1 → https://api.anthropic.com/mcp/gdrive/mcp
https://gmailmcp.googleapis.com/mcp/v1 → https://gmail.mcp.claude.com/mcp
https://calendarmcp.googleapis.com/mcp/v1 → https://gcal.mcp.claude.com/mcp
RUNTIME BEHAVIOR
Calling a Drive tool through a managed agent session with the stored credential returns:
"This MCP server has been turned down. Please use https://drivemcp.googleapis.com/mcp/v1 instead — connect via https://claude.ai/directory/connectors/google-drive-drivemcp."
So the rewritten URL routes to a decommissioned backend. Same behavior for Gmail and Calendar (server URL not found at gmail.mcp.claude.com/mcp and gcal.mcp.claude.com/mcp).
WHAT WE NEED
Either:
(a) Disable the URL normalization so we can store the *.googleapis.com/mcp/v1 URLs the public migration message instructs us to use, or
(b) Repoint the stored URLs (api.anthropic.com/mcp/gdrive/mcp, gmail.mcp.claude.com/mcp, gcal.mcp.claude.com/mcp) to the new backends so existing credentials become live without recreation.
OAuth tokens behind these credentials are valid Google-side; the block is entirely on the Anthropic gateway layer.
This blocks our MCP attachment to 16 managed agents. Other vault credentials in the same org (Slack, GitHub, Lovable, Calendly, Zoom, Gamma, Close, Canva) route correctly at session time, so the issue is specific to the Google connectors.
Environment: Claude Managed Agents, Anthropic Python/Node SDK, vault credentials API
Date observed: 2026-05-27
SUMMARY
When creating MCP credentials for Google Drive, Gmail, and Calendar via vaults.credentials.create, the API rewrites the mcp_server_url I submitted to a different URL server-side. The rewritten URL points to a backend that returns "This MCP server has been turned down" at tool-call time. mcp_server_url is documented as immutable after creation, so we cannot patch existing credentials.
REPRO
Using the official @anthropic-ai/sdk Node client (latest), authenticated as admin:
await client.vaults.credentials.create({
vault_id: ,
name: "google-drive",
mcp_server_url: "https://drivemcp.googleapis.com/mcp/v1",
oauth_token: { access_token: "", refresh_token: "" }
});
Then vaults.credentials.retrieve() returns mcp_server_url = "https://api.anthropic.com/mcp/gdrive/mcp", not the URL we sent.
OBSERVED REWRITES (sent → stored)
https://drivemcp.googleapis.com/mcp/v1 → https://api.anthropic.com/mcp/gdrive/mcp
https://gmailmcp.googleapis.com/mcp/v1 → https://gmail.mcp.claude.com/mcp
https://calendarmcp.googleapis.com/mcp/v1 → https://gcal.mcp.claude.com/mcp
RUNTIME BEHAVIOR
Calling a Drive tool through a managed agent session with the stored credential returns:
"This MCP server has been turned down. Please use https://drivemcp.googleapis.com/mcp/v1 instead — connect via https://claude.ai/directory/connectors/google-drive-drivemcp."
So the rewritten URL routes to a decommissioned backend. Same behavior for Gmail and Calendar (server URL not found at gmail.mcp.claude.com/mcp and gcal.mcp.claude.com/mcp).
WHAT WE NEED
Either:
(a) Disable the URL normalization so we can store the *.googleapis.com/mcp/v1 URLs the public migration message instructs us to use, or
(b) Repoint the stored URLs (api.anthropic.com/mcp/gdrive/mcp, gmail.mcp.claude.com/mcp, gcal.mcp.claude.com/mcp) to the new backends so existing credentials become live without recreation.
OAuth tokens behind these credentials are valid Google-side; the block is entirely on the Anthropic gateway layer.
This blocks our MCP attachment to 16 managed agents. Other vault credentials in the same org (Slack, GitHub, Lovable, Calendly, Zoom, Gamma, Close, Canva) route correctly at session time, so the issue is specific to the Google connectors.