Cursor’s Slack connector can be signed into only one Slack workspace at a time

Ideas Feature Requests
,
1

Feature request for product/service

3rd Party Extensions

Describe the request

Cursor’s Slack connector binds the session to a single Slack workspace. Connecting another workspace replaces the first. That blocks corporate use on Slack Enterprise Grid, where one company has many workspaces (for example product teams) and staff need to search and post across them in one Cursor session.

The suggested workaround (per-project MCP config, see How do we configure workspace-specific plugin MCP servers) does not help. Those workspaces share the same SSO identity. Extra mcp.json entries still collide on one OAuth grant, not one grant per Grid workspace.

What we need:

Keep several company Slack workspaces connected at once under the same Slack SSO user
Let the agent pick a workspace (or use the one implied by channel ID) without logging out and reconnecting
Do not require a separate Slack user or a different IdP login per workspace

Follow up from: How do we configure workspace-specific plugin MCP servers

5

Hey @Eugene_Eichelberger, thanks for the detailed write-up, and for linking the earlier thread.

You’ve read the current behavior correctly. Cursor keys the Slack connection to the server address, so two entries that both point at Slack’s MCP end up sharing one login, and whichever workspace you authorize last wins. The team is working on giving each entry its own independent login so several Grid workspaces can stay connected side by side!

As a company recently having gone through an acquisition, we feel the pain too.