Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Scheduled task MCP connector tools unavailable in execution environment (Slack, Notion, Gmail, Calendar all fail) [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#45306•Fetched 2026-04-09 08:08:26
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
thomask-systhomask-sys
Participants
github-actions[bot]github-actions[bot]thomask-systhomask-sys
Timeline (top)
labeled ×3commented ×1

Error Message

Error Messages/Logs

Root Cause

All scheduled tasks fail silently because MCP connector tools are not injected into the execution environment. Every run shows the agent only has access to WebFetch, WebSearch, RemoteTrigger, and file system tools. Connected connectors (Slack, Notion, Gmail, Google Calendar, Granola) do not appear as callable tools, so the agent cannot complete any action.

Code Example

From run transcript:
"I don't have a Slack tool available in this environment."
"I'm unable to run the morning briefing — the required integrations are not available in this environment."
"What's currently available: only web fetch, web search, and file system tools."

permitted_tools arrays in trigger job_config are correctly populated (confirmed via API), but tools do not load at runtime.
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?

All scheduled tasks fail silently because MCP connector tools are not injected into the execution environment. Every run shows the agent only has access to WebFetch, WebSearch, RemoteTrigger, and file system tools. Connected connectors (Slack, Notion, Gmail, Google Calendar, Granola) do not appear as callable tools, so the agent cannot complete any action.

The agent responds: "I don't have a Slack tool available in this environment" / "the required integrations are not available in this environment."

This affects:

  • Triggers created via the API
  • Triggers created fresh through the web UI at claude.ai/code/scheduled
  • All connector types tested: Slack, Notion, Gmail, Google Calendar, Granola

Last successful run was approximately April 2, 2026. All runs since then produce no output — no Slack messages, no Notion updates.

What Should Happen?

Connected MCP connectors should inject their tools into scheduled task execution sessions, exactly as they do in interactive claude.ai and Claude Code (VS Code) sessions. A trigger with Slack connected and Always Allow permissions should have Slack tools available at runtime.

Error Messages/Logs

From run transcript:
"I don't have a Slack tool available in this environment."
"I'm unable to run the morning briefing — the required integrations are not available in this environment."
"What's currently available: only web fetch, web search, and file system tools."

permitted_tools arrays in trigger job_config are correctly populated (confirmed via API), but tools do not load at runtime.

Steps to Reproduce

  1. Go to claude.ai/code/scheduled
  2. Create a new scheduled task
  3. Add the Slack connector, set to Always Allow all tools
  4. Set prompt to: "Send me a Slack DM saying 'test'"
  5. Click Run Now
  6. Open the run transcript — agent reports no Slack tool available and only sees WebFetch/WebSearch

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.81

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Session link: https://claude.ai/code/session_01A5r7ZSpgPMWWioNQSxowaS

extent analysis

TL;DR

The most likely fix is to investigate and resolve the issue with MCP connector tools not being injected into the execution environment, potentially related to a regression in the Claude Code version.

Guidance

  • Verify that the permitted_tools arrays in the trigger job_config are correctly populated and match the expected tools, including Slack.
  • Check the Claude Code version history to identify any changes related to MCP connector tool injection, as this issue is reported as a regression.
  • Test the scheduled task with a different connector, such as Notion or Gmail, to see if the issue is specific to Slack or a broader problem with MCP connector tools.
  • Review the run transcript and error messages to ensure that the issue is not related to permissions or configuration, but rather the availability of the tools at runtime.

Example

No code snippet is provided, as the issue is related to the execution environment and tool availability, rather than a specific code problem.

Notes

The issue is reported as a regression, and the last working version is not specified, which may indicate that the problem is related to a recent change in the Claude Code version. The fact that the permitted_tools arrays are correctly populated, but the tools do not load at runtime, suggests a potential issue with the tool injection mechanism.

Recommendation

Apply workaround: Try to identify and revert any recent changes related to MCP connector tool injection, or wait for an updated version of Claude Code that addresses this regression.

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#callback error#memory management#API rate limit#retriever error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING