Cursor/Slack MCP Oauth is broken

Support Bug Reports
, , , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Slack MCP/Plugin Oauth is broken.
Users in my org are trying to connect to slack through the MCP or Plugin and neither are working. My instance was grandfathered in from installing in Early April and was working today. I disconnected and uninstalled the plugin and attempted to reinstall and reconnect and now I get an error from slack saying I’m not authorized to install cursor in my org’s slack.

When I check the approved slack apps for my org, Cursor is an installed app and it shows my user still has access. I even still have the Cursor app in slack, which appears to still be connected. It’s the MCP itself that’s having issues. The connection to the IDE is not

Steps to Reproduce

  1. install slack plugin or MCP
  2. click connect
  3. Does not Oauth properly

Expected Behavior

When connecting to the plugin or mcp I should reach the scope page with the ability to connect cursor to slack.

Screenshots / Screen Recordings

slackoauth.png
slackoauth.png524×176 9.01 KB

Operating System

MacOS

Version Information

Version: 3.2.21
VSCode Version: 1.105.1
Commit: 806df57ed3b6f1ee0175140d38039a38574ec720
Date: 2026-05-03T01:46:14.413Z (2 days ago)
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Additional Information

Users started reporting the connection was no longer working starting Sunday, May 2nd, 2026.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

ditto

7

This error comes from Slack’s app approval system, not from Cursor. Here’s what’s happening: your Slack workspace has app approval policies that control who can install or re-authorize apps. Since you were previously connected (from early April), your auth was still valid. But once you disconnected and tried to re-authorize, Slack’s approval gate kicked in and is now blocking the new auth attempt.

To fix this, a Slack workspace admin needs to:

  1. In Slack, click the admin cog in the left sidebar

  2. Select Apps & Workflows

  3. Click Resolutions > Denied apps tab

  4. Look for Cursor — if it’s there, click the three dots > Approve for this workspace > Approve

If Cursor doesn’t appear in the Denied tab, have your admin check under the Restricted section as well. Once the app is approved/unrestricted at the workspace level, regular members should be able to complete the OAuth flow again.

We’re also tracking a broader cluster of Slack MCP auth improvements on our side. If the steps above don’t resolve it, let me know and I can dig deeper.