CCR scheduled triggers: claude.ai MCP connectors not available in remote session

Resolved 💬 4 comments Opened Apr 1, 2026 by cwu-ts Closed Apr 5, 2026

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?

Description

When a scheduled CCR trigger has mcp_connections configured with claude.ai OAuth connectors (Atlassian, Slack, Gmail), the MCP tools are not available in the remote session's tool registry. The agent cannot find them via ToolSearch and reports them as not connected.

Steps to Reproduce

  1. Create a scheduled trigger at claude.ai/code/scheduled with claude.ai MCP connectors attached (e.g., Atlassian, Slack, Gmail)
  2. Run the trigger (via schedule or manually via the run API)
  3. In the remote CCR session, attempt to use the MCP tools (e.g., mcp__claude_ai_Atlassian__searchJiraIssuesUsingJql)
  4. The tools are not found — they don't appear in the deferred tool registry

Expected Behavior

MCP tools from connectors configured in mcp_connections should be available in the remote CCR session's tool registry.

Actual Behavior

The tools don't appear in the deferred tool registry. The remote agent reports:

"The required MCP tools (mcp__claude_ai_Atlassian, mcp__claude_ai_Slack, mcp__claude_ai_Gmail) are not available in this environment — they don't appear in the deferred tool registry."

Additional Context

  • Trigger ID: trig_01SuHNpZRr2LST3wBfnLvgHy
  • Connectors configured: Atlassian, Slack, Gmail (all visible in trigger UI at claude.ai/code/scheduled)
  • Regression: The trigger worked correctly on 2026-03-31 and started failing on 2026-04-01
  • Environment: Default CCR environment

What Should Happen?

MCP tools from connectors configured in mcp_connections should be available in the remote CCR session's deferred tool registry, allowing the agent to call them via ToolSearch and use them normally.

Error Messages/Logs

Steps to Reproduce

  1. Create a scheduled trigger at claude.ai/code/scheduled with claude.ai MCP connectors attached (Atlassian, Slack, Gmail)
  2. Run the trigger via the run API or wait for it to fire on schedule
  3. In the remote CCR session, the agent attempts to use MCP tools (e.g., mcp__claude_ai_Atlassian__searchJiraIssuesUsingJql)
  4. The tools are not found — they don't appear in the deferred tool registry via ToolSearch

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.89 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗