Schedule skill / RemoteTrigger API doesn't see MCP connectors connected on Team workspace

Preflight Checklist

• [x] I have searched existing requests and this hasn't been reported yet
• [x] This is a single bug report

Summary

The schedule skill (and the underlying RemoteTrigger API used to attach MCP connectors to routines) returns an empty connector list for users on a Team workspace, even when connectors are actually connected and working at https://claude.ai/customize/connectors.

This makes it impossible to attach Gmail, Notion, Slack, etc. to a remote routine from a Team workspace — routines can only output to the run history page, with no path to push notifications via email/Slack/etc.

Steps to Reproduce

1. Be a member of a Team workspace on claude.ai (Plano Team / Admin role)
2. Connect Gmail at https://claude.ai/customize/connectors — confirm it appears under Web connectors with full permissions granted
3. In Claude Code Desktop (same account, same workspace), invoke /schedule and try to create or update a routine with an MCP connection
4. Observe the skill output: Available MCP Connectors: No connected MCP connectors found.

Expected Behavior

The skill should list the Gmail connector (and any other connector connected on the workspace) with a connector_uuid, name, and URL, so it can be attached to the routine via mcp_connections.

Actual Behavior

The connector list is empty, despite the connector being:

• Visible and enabled at claude.ai/customize/connectors
• Listed in ~/.claude.json under claudeAiMcpEverConnected (e.g. \"claude.ai Gmail\")
• Absent from ~/.claude/mcp-needs-auth-cache.json (i.e., not flagged as needing re-auth)
• Functional locally — the corresponding mcp__<uuid>__list_labels, search_threads, etc. tools work in the Desktop app right now

The runtime UUID exposed in the local tool names (e.g. mcp__5ae9218e-2353-49be-acfc-7c4fe7471de8__list_labels) does not appear to be the same as the connector_uuid expected by the routines API — it is not persisted to .claude.json or any visible config, so users cannot manually fill in the field as a workaround.

Impact

• Routines on Team workspaces can't deliver results via email/Slack/etc., losing a major piece of the value proposition (push notifications for monitoring tasks)
• The skill silently directs users to https://claude.ai/customize/connectors for connectors that are already connected, leading to confusion (\"I connected it three times — why doesn't it show up?\")
• Multi-account / multi-workspace users have no diagnostic to tell whether they're hitting a permission/scope issue vs. a UI bug

Hypothesis

The RemoteTrigger / routines API appears to query a different scope than the /customize/connectors page — likely individual user scope vs. workspace scope. Connectors installed at the Team workspace level seem not to be exposed to the routines API.

Environment

• Claude Code Desktop on Windows 11 (also reported by user via desktop app + web at claude.ai)
• CLI version 2.1.121
• Account: Team plan, Admin role
• Affected connectors confirmed: Gmail (others on the workspace likely affected too: Notion, Google Drive, GitHub, Intuit QuickBooks)
• Both Desktop app and claude.ai web logged into the same email and same workspace

Workaround

Manual pull: leave routine without MCP connections, output goes to the run history page, user opens a session and asks Claude to fetch the latest result via RemoteTrigger get. This works but defeats the purpose of automated push notifications.

Suggested Fix

Either:

1. Make the routines API surface workspace-scoped connectors the same way /customize/connectors does, OR
2. If there's a real permission boundary, return a clear error from the skill (\"Workspace connectors are not yet supported on routines — only personal connectors\") instead of silently returning an empty list, OR
3. Document the limitation explicitly so users on Team workspaces don't burn time troubleshooting.