claude.ai managed MCP connectors still unavailable in --print mode on v2.1.202 (regression of #36587)

Open 💬 0 comments Opened Jul 7, 2026 by egatuna

Environment

  • Claude Code v2.1.202 (npm global install), macOS (Darwin 25.5.0)
  • Auth: Max-plan claude.ai login (claudeAiOauth in ~/.claude/.credentials.json)

Summary

#36587 / #36833 were closed as fixed in v2.1.83 ("claude.ai-managed MCP connectors are
now available in --print mode") and are now locked. On v2.1.202 the behavior has
regressed (or the fix does not cover this configuration): claude.ai connectors never
attach to -p sessions.

Repro

  1. claude mcp list -> claude.ai connectors report Connected (Gmail, Google Calendar,

Google Drive, Jotform, Canva, Indeed, ...).

  1. Same connectors work normally in interactive sessions (tools appear as

mcp__claude_ai_*).

  1. `claude -p "List the names of your available MCP tools that start with

mcp__claude_ai, as a comma-separated list. If none, say NONE." --output-format text`
-> "NONE". Only user-scoped MCP servers (a locally configured one) attach.

  1. Same result with explicit `--allowedTools "mcp__claude_ai_Jotform"

"mcp__claude_ai_Google_Calendar" "mcp__claude_ai_Gmail"`.

Expected

-p sessions attach the account's claude.ai managed connectors, as fixed in v2.1.83
per #36587.

Notes

  • disableClaudeAiConnectors is not set in any settings file.
  • User-scoped MCP servers DO load in -p, so this is specific to the claude.ai

managed-connector fetch path in non-interactive mode.

  • Timeline data point: connectors briefly worked from headless claude -p (cron) on

2026-07-04 early afternoon, then stopped ~15:30 the same day on the same installed
version, which may indicate a server-side component.

View original on GitHub ↗