Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Slack-initiated Claude Code sessions missing account-level MCP connectors [2 comments, 3 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#49010•Fetched 2026-04-17 08:53:22
View on GitHub
Comments
2
Participants
3
Timeline
12
Reactions
0
Author
jagregoryjagregory
Participants
0xbrainkid0xbrainkidauthora-ariaauthora-ariajagregoryjagregory
Timeline (top)
labeled ×6commented ×2cross-referenced ×2mentioned ×1

Error Message

Error Messages/Logs

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?

When Claude Code is initiated via Slack (@Claude mention routed to Code mode), the session only receives the GitHub MCP. All account-level MCP connectors (Atlassian, Sentry, incident.io, Slack) are missing.

The same connectors are fully available when:

  • Creating a Claude Code session directly from the web (claude.ai/code) in the same cloud environment
  • Using Chat mode in the same Slack workspace

Tested with both lazy and eager tool loading — no difference. The connectors are simply not present in the session regardless of loading strategy. Connectors do not appear after talking with the agent.

Session IDs

  • session_016L68jvFnsJL7uZ3CqbBqGU — created via Slack → Code. Only has GitHub MCP.
  • session_01HQHWQb2CX42f77MoEhBuhH — created via Claude Code web. Has all MCPs (GitHub, Atlassian, Sentry, incident.io, Slack).

Actual Behavior

EntrypointGitHubAtlassianSentryincident.ioSlack MCP
Web → Code✅✅✅✅✅
Slack → Chat✅✅✅✅✅
Slack → Code✅❌❌❌❌

Related Issues

  • #15884 — Previously the inverse: GitHub was missing from Slack → Code while MCP connectors worked. Appears that fix resolved GitHub propagation but account-level MCP connectors are still not injected.
  • #42033 — Cloud scheduled tasks also don't receive account-level MCP connectors
  • #43397 — Same pattern across multiple entrypoints; noted as a platform infrastructure issue

What Should Happen?

I expect to see the same MCPs in both sessions.

Error Messages/Logs

Steps to Reproduce

  1. Configure account-level connectors (Atlassian, Sentry, incident.io, Slack) at claude.ai/settings/connectors — all show as connected
  2. In Slack, send a message routed to Claude Chat: "what MCPs do you have" → returns all 4 connectors + GitHub
  3. In Slack, send a message routed to Claude Code: "what MCPs do you have" → returns only GitHub
  4. Open a Claude Code session on the web for the same repo → all 5 MCPs are present
  5. In both Code sessions, claude mcp list returns empty — MCPs are harness-injected, not CLI-configured
  6. Tested with both lazy and eager tool loading — same result

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

web

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

No response

extent analysis

TL;DR

The issue can be addressed by investigating the differences in how account-level MCP connectors are injected between Slack-initiated Code sessions and web-initiated Code sessions.

Guidance

  • Review the code responsible for injecting MCP connectors in both entrypoints (Slack → Code and web → Code) to identify any discrepancies.
  • Compare the session initialization processes for both entrypoints to ensure that account-level MCP connectors are being properly propagated.
  • Investigate the role of the Anthropic API in injecting MCP connectors and whether it differs between the two entrypoints.
  • Examine the related issues (#15884, #42033, #43397) to see if they provide any insight into the problem or potential solutions.

Example

No code snippet is provided as the issue does not contain sufficient information to create a relevant example.

Notes

The issue seems to be related to the platform infrastructure, as noted in #43397. The fact that the same connectors are available when creating a session directly from the web or using Chat mode in the same Slack workspace suggests that the issue is specific to the Slack → Code entrypoint.

Recommendation

Apply workaround: Investigate and address the discrepancies in MCP connector injection between the two entrypoints, as this is likely the root cause of the issue. This approach is recommended because it targets the suspected source of the problem and may provide a more permanent solution.

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#dependency error#configuration error#environment variable#network 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