Feature Request
The built-in Slack MCP connector currently supports only one workspace per Claude account. There is no way to add a second workspace through the UI or configuration.
Use Case
Many professionals work across multiple Slack workspaces -- for example, a consultant with their own company workspace and a client workspace, or a founder who advises other companies. Today, connecting workspace #1 is one click. Connecting workspace #2 requires setting up a self-hosted MCP server from scratch: downloading a third-party binary, creating a Slack app manually at api.slack.com, configuring seven OAuth scopes, writing MCP JSON config with the correct CLI flags, and restarting Claude Code.
Request
Allow users to authorize multiple Slack workspaces through the same built-in connector that makes the first workspace so easy. Even supporting two would cover the majority of multi-workspace users.
Feature Request
The built-in Slack MCP connector currently supports only one workspace per Claude account. There is no way to add a second workspace through the UI or configuration.
Use Case
Many professionals work across multiple Slack workspaces -- for example, a consultant with their own company workspace and a client workspace, or a founder who advises other companies. Today, connecting workspace #1 is one click. Connecting workspace #2 requires setting up a self-hosted MCP server from scratch: downloading a third-party binary, creating a Slack app manually at api.slack.com, configuring seven OAuth scopes, writing MCP JSON config with the correct CLI flags, and restarting Claude Code.
Request
Allow users to authorize multiple Slack workspaces through the same built-in connector that makes the first workspace so easy. Even supporting two would cover the majority of multi-workspace users.