LinkedIn Content Engine Automation Schedule Connection Bug

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Title: Scheduled routines (/schedule, RemoteTrigger) report zero connected MCP connectors despite account showing them as Connected

Environment: Claude Code, macOS (Darwin), [date: 2026-07-23]

Summary:
The Connectors settings page (Settings → Connectors) shows Gmail, Slack, Google Drive, Notion, Attio, and HeyReach all connected (green checkmarks). However, the scheduled-routines feature (/schedule, backed by the RemoteTrigger tool used to create recurring cloud agents) consistently reports no connected MCP connectors are available to attach to a routine — meaning I can't get a connector_uuid to wire Slack/Gmail into a routine's mcp_connections. i have also attached a screen shot as well for your reference.

Steps to reproduce:

Connect Slack and Gmail at Settings → Connectors — confirm both show "Connected."
Invoke /schedule (or otherwise trigger routine creation).
Check the "Available MCP Connectors" list the schedule flow surfaces before creating a routine.
Expected behavior: Slack and Gmail (and the other connected apps) should appear as available connectors with a connector_uuid, ready to attach to a new routine.

Actual behavior: The list is empty every time — checked 3 separate times over roughly a 20-minute window, both immediately after connecting and after waiting, with the same "no connected MCP connectors" result each time. A separate connector-lookup tool (list_connectors / search_mcp_registry) also returns zero installed connectors, suggesting this isn't isolated to the scheduling flow specifically — it looks like the routine/connector-registry backend isn't reading from the same source as the account-level Connectors settings page.

Impact: Blocks building any scheduled cloud routine that needs to act on a connected service (e.g., sending a Slack message or email on a schedule) — the routine can be created, but can't be given access to services the account has already authorized.

<img width="2000" height="1410" alt="Image" src="https://github.com/user-attachments/assets/d4e6e290-7fae-42aa-8c8b-f436cc5f119a" />

What Should Happen?

Any service shown as "Connected" on the Settings → Connectors page (in my case: Gmail, Slack, Google Drive, Notion, Attio, HeyReach) should appear as an available connector — with a connector_uuid — when creating a scheduled cloud routine via /schedule (backed by the RemoteTrigger API). This would let the routine actually use that service (e.g., send a Slack message or draft an email) on its schedule. The connector registry that /schedule reads from should be the same one the Connectors settings page writes to.

Error Messages/Logs

No explicit error is thrown — the failure is a silent empty result. Exact outputs observed:

From the /schedule flow's "Available MCP Connectors" section:

No connected MCP connectors found. The user may need to connect servers at https://claude.ai/customize/connectors
From the connector-lookup tool (list_connectors):

{"connectors":[],"keywords":[],"note":"No installed connectors found — the card did not render. Offer to search the registry (search_mcp_registry)."}
From the connector search tool (search_mcp_registry) with keywords ["slack","gmail","email"]:

{"results":[]}
This was checked 4 separate times over roughly 45 minutes — both immediately after connecting Gmail/Slack and after waiting — and once more after updating Claude Code from version 2.1.114 to the latest (2.1.218) via claude update. The result was identical every time, ruling out both a short-lived cache issue and a client-version issue.

Steps to Reproduce

Go to Settings → Connectors in Claude Code and connect at least one service (e.g., Gmail or Slack). Confirm it shows a green checkmark / "Connected" status.
Start the scheduled-routine creation flow (/schedule).
Look at the "Available MCP Connectors" section shown before you create a routine.
Observe it reports zero connectors, even though step 1's service is clearly connected.
(Confirms it's not transient) Wait several minutes, or run claude update to get the latest version, and repeat steps 2–3 — the empty result persists.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.218

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_