schedule skill: setup-time 'No connected MCP connectors found' but 9 connectors auto-attach at routine creation

Summary

The schedule skill's setup-time preamble reports "No connected MCP connectors found. The user may need to connect servers at https://claude.ai/customize/connectors" — but the user actually has multiple connectors configured at claude.ai. When the routine is created seconds later via RemoteTrigger create, the response payload includes a populated mcp_connections array with all of those connectors auto-attached. Two server-side queries appear to be reading two different views of the same fact and disagreeing.

Why this matters

Agents reading the skill's setup notes treat the "no connectors" assertion as ground truth and design routines around the assumption of a bare cloud sandbox (no Gmail, no Calendar, no Supabase, etc.). When the routine actually runs Tuesday morning, it has all those MCPs attached but the prompt was written assuming none — so the agent doesn't use them.

In my case I built a Tuesday check-in routine that fell back to a "GitHub issue only" notification path because I believed Gmail wasn't available. The user pushed back, I inspected the RemoteTrigger create response, and Gmail / Calendar / Drive / Supabase / Vercel / Granola / MailerLite / Stripe / Figma were all in mcp_connections. The setup note was wrong; I had to update the routine.

Reproduction

1. As a user with multiple MCP connectors configured at claude.ai/customize/connectors, invoke /schedule from Claude Code.
2. Observe the skill preamble. The "Available MCP Connectors" section reads:

> No connected MCP connectors found. The user may need to connect servers at https://claude.ai/customize/connectors

1. Proceed to create a routine via RemoteTrigger.
2. Inspect the response payload. The mcp_connections array is fully populated with the user's connectors (Supabase, Vercel, Granola, MailerLite, Stripe, Figma, Gmail, Calendar, Drive in this case).

Expected

The skill preamble's "Available MCP Connectors" section should list the connectors that will actually be auto-attached to the routine at creation time. They should match.

Actual

The skill says zero. The routine creation response says nine. Disagreement.

Evidence

• Routine ID: trig_01FnL89aWKWr7CWtVvQRx6oX
• Created: 2026-05-03T19:21:54Z
• Account: 0c3fe177-9a3a-4fb2-b553-267205f445be
• Connectors that DID auto-attach despite the skill saying none:
• Gmail (cb05ed4b-eb84-4c6e-b6d7-4e00e631a149)
• Calendar (e93c28fc-0962-412f-9e00-a9dfc853a300)
• Drive (3e83e1ac-c2a3-4ebf-99bc-90015fac5116)
• Supabase (bc47745d-befe-4a97-9659-285927359b3e)
• Vercel (f6be1213-dc81-49b2-a129-eb8987f76359)
• Granola (3df9b906-f6fa-4f40-bf49-77af34c2c983)
• MailerLite (c03bdcee-8bad-4a64-8e90-b1d4e9e2aa51)
• Stripe (5915cbea-0b89-4af7-bd93-7be066ba6e94)
• Figma (ef06595a-bd9a-409b-a90d-420d15be7ed5)

Workaround

After calling RemoteTrigger create, parse the response's mcp_connections array as the source of truth. If it contains MCPs that the skill's setup note said weren't there, update the routine prompt with RemoteTrigger update to actually use them.

Suggested fix

Whatever query backs the skill's setup-time MCP discovery should hit the same source as the auto-attach logic in routine creation. Either both should query the user's claude.ai connector list, or both should query the routine's account-level attached-MCPs list. Right now they're querying different things and one of them returns empty.