Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] /schedule skill doesn't surface custom MCP connectors for routine attachment [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#55641•Fetched 2026-05-03 04:48:11
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
rbl-itayrbl-itay
Participants
github-actions[bot]github-actions[bot]rbl-itayrbl-itay
Timeline (top)
labeled ×5commented ×1

Error Message

Error Messages/Logs

Fix Action

Fix / Workaround

▎ The /schedule skill in Claude Code consistently reports "No connected MCP connectors found" even when custom connectors are connected and
▎ active on claude.ai's connectors directory. ▎
▎ Reproduction: ▎ 1. On claude.ai, add a custom connector (e.g., Vercel via https://mcp.vercel.com) and complete the OAuth flow. ▎ 2. Verify it appears under Settings → Connectors with status "Connected" and tools listed.
▎ 3. In Claude Code (CLI), invoke /schedule to create a routine.
▎ 4. The skill's "Available MCP Connectors" section lists none.
▎
▎ Expected: Custom connectors connected to the same Claude account should be available to attach to a routine via mcp_connections in the
▎ routine config.
▎
▎ Actual: Skill reports no connectors. There's no connector_uuid exposed to the user, so the routine config can't reference it. This blocks
▎ any routine that needs to use a custom connector (e.g., a scheduled "check Vercel deployment health" agent). ▎
▎ Environment:
▎ - Claude Code CLI (latest) ▎ - macOS ▎ - Tested with Vercel MCP custom connector (https://mcp.vercel.com) ▎ - Account confirmed via screenshot showing connector is active in Claude app
▎
▎ Workaround: None. Forced to schedule routines without the connector and lose the read-access the connector would have provided.

Workaround: None. Forced to schedule routines without the connector and lose the read-access the connector would have provided.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

▎ The /schedule skill in Claude Code consistently reports "No connected MCP connectors found" even when custom connectors are connected and
▎ active on claude.ai's connectors directory. ▎
▎ Reproduction: ▎ 1. On claude.ai, add a custom connector (e.g., Vercel via https://mcp.vercel.com) and complete the OAuth flow. ▎ 2. Verify it appears under Settings → Connectors with status "Connected" and tools listed.
▎ 3. In Claude Code (CLI), invoke /schedule to create a routine.
▎ 4. The skill's "Available MCP Connectors" section lists none.
▎
▎ Expected: Custom connectors connected to the same Claude account should be available to attach to a routine via mcp_connections in the
▎ routine config.
▎
▎ Actual: Skill reports no connectors. There's no connector_uuid exposed to the user, so the routine config can't reference it. This blocks
▎ any routine that needs to use a custom connector (e.g., a scheduled "check Vercel deployment health" agent). ▎
▎ Environment:
▎ - Claude Code CLI (latest) ▎ - macOS ▎ - Tested with Vercel MCP custom connector (https://mcp.vercel.com) ▎ - Account confirmed via screenshot showing connector is active in Claude app
▎
▎ Workaround: None. Forced to schedule routines without the connector and lose the read-access the connector would have provided.

What Should Happen?

Workaround: None. Forced to schedule routines without the connector and lose the read-access the connector would have provided.

Error Messages/Logs

Steps to Reproduce

Reproduction: ▎ 1. On claude.ai, add a custom connector (e.g., Vercel via https://mcp.vercel.com) and complete the OAuth flow. ▎ 2. Verify it appears under Settings → Connectors with status "Connected" and tools listed.
▎ 3. In Claude Code (CLI), invoke /schedule to create a routine.
▎ 4. The skill's "Available MCP Connectors" section lists none.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.121

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue can be resolved by ensuring that the custom connectors are properly configured and exposed to the Claude Code CLI, potentially by verifying the connector's UUID and updating the routine config.

Guidance

  • Verify that the custom connector is correctly set up in the Claude app and its status is "Connected" with tools listed.
  • Check if the connector's UUID is exposed to the user and can be referenced in the routine config.
  • Investigate potential configuration issues between the Claude Code CLI and the custom connector, ensuring that the connector is properly registered and accessible.
  • Review the Claude Code documentation to see if there are specific requirements or limitations for using custom connectors with the /schedule skill.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The issue may be related to a configuration or exposure problem rather than a bug in the Claude Code itself. Further investigation into the connector setup and routine config is needed to determine the root cause.

Recommendation

Apply workaround: Verify and update the custom connector configuration to ensure it is properly exposed to the Claude Code CLI, as this is the most likely cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#parallel task#integration issue#index setup#retrieval issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] /schedule skill doesn't surface custom MCP connectors for routine attachment [1 comments, 2 participants]