claude-code - 💡(How to fix) Fix [FEATURE] Add support for private channels in Slack MCP integration [1 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#55957Fetched 2026-05-05 06:01:56
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×2closed ×1
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

Currently, the Slack MCP integration's slack_list_channels tool only returns public channels. It would be valuable to also support private channels when the bot has been invited and has the appropriate permissions.

Proposed Solution

Desired Behavior:

  • Return both public and private channels that the bot is a member of
  • Respect the bot's groups:read OAuth scope to access private channels

Alternative Solutions

No response

Priority

Medium - Would be very helpful

Feature Category

MCP server integration

Use Case Example

Benefits:

  • Full Slack workspace coverage
  • Ability to work with sensitive/private discussions
  • Better team collaboration in secure channels

Additional Context

we want to streamline our workflow in designing and planning, so we want claude code to access slack to automatically display the design details in canvas app on slack

extent analysis

TL;DR

Modify the Slack MCP integration's slack_list_channels tool to include private channels by utilizing the bot's groups:read OAuth scope.

Guidance

  • Review the Slack API documentation to ensure the bot has the necessary permissions to access private channels.
  • Update the slack_list_channels tool to use the conversations.list method with the types parameter set to public_channel,private_channel to retrieve both public and private channels.
  • Verify that the bot has been invited to the private channels and has the appropriate permissions to access them.
  • Test the updated slack_list_channels tool to ensure it returns both public and private channels that the bot is a member of.

Example

No code example is provided as the issue does not contain sufficient technical details.

Notes

The solution assumes that the Slack API and the bot's OAuth scope are properly configured to support private channel access.

Recommendation

Apply workaround: Modify the slack_list_channels tool to utilize the bot's groups:read OAuth scope to access private channels, as this will provide the desired functionality without requiring a full upgrade.

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…

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 [FEATURE] Add support for private channels in Slack MCP integration [1 participants]