## Summary An MCP connector that is actively connected at claude.ai/customize/connectors is not visible/attachable when creating a Cloud Routine (RemoteTrigger / `/schedule`). ## Environment - Claude Code desktop app (Windows) - Feature: Cloud Routines (RemoteTrigger tool / `/schedule` skill) ## Steps to reproduce 1. Connect a connector at `claude.ai/customize/connectors` (tested with Google Calendar, type "Web"). The Konnektoren settings page shows it as "Verbunden" with a green checkmark. 2.

Connected MCP connector (e.g. Google Calendar) not available for Cloud Routines / RemoteTrigger

Status Open

Maintainer reply None cached

Activity 0 comments · opened Aug 17, 2026

Summary

An MCP connector that is actively connected at claude.ai/customize/connectors is not visible/attachable when creating a Cloud Routine (RemoteTrigger / /schedule).

Environment

Claude Code desktop app (Windows)
Feature: Cloud Routines (RemoteTrigger tool / /schedule skill)

Steps to reproduce

Connect a connector at claude.ai/customize/connectors (tested with Google Calendar, type "Web"). The Konnektoren settings page shows it as "Verbunden" with a green checkmark.
Invoke the /schedule skill (or otherwise request creation of a Cloud Routine) to create a routine that should use that connector via mcp_connections.
Check the "Available MCP Connectors" section returned by the skill.

Expected behavior

The connected connector (e.g. Google Calendar) should appear in the list of connectors available to attach to a Cloud Routine, with its connector_uuid, sanitized name, and URL.

Actual behavior

The connector list is consistently empty ("No available MCP connectors found."), even though:

The connector shows as actively "Verbunden" (Web type) on the Konnektoren settings page (confirmed via screenshot).
The skill was re-invoked multiple times over several minutes (to rule out a short caching delay) — result was identical every time.
A separate connector-listing tool available in the app (unrelated to RemoteTrigger) also reported zero installed connectors, consistent with the routines-side view.

This suggests "Web" type connectors added via the Konnektoren page are not currently being surfaced to the Cloud Routines / RemoteTrigger connector-attachment system, even though they work fine elsewhere (e.g. directly in-app for calendar access).

Impact

Cannot create Cloud Routines that depend on an MCP connector (e.g. Google Calendar) to run scheduled checks independently of whether the local machine is on. This blocks a fairly common use case: a scheduled cloud agent that needs to read/write a connected calendar.

View original on GitHub ↗