This also blocks new Slack MCP / Slack plugin auth in the Cursor IDE. Existing Cursor Slack installs keep working (old token / old scope set). A workspace admin cannot add those two scopes from Slack — they are not on the installed Cursor app, there is no app-request to approve, and Marketplace only shows Open in Slack (no Add to Slack).
Looks like the same class of issue as this May 2026 unapproved-scopes thread: Cursor’s OAuth request includes scopes that are not yet approved on the published Cursor Slack app.
Please add links:read and links:write to the published Cursor Slack app (A08SKDT6QUW) so new installs / reconnects can complete.
Cursor 3.17.19 (stable, macOS 26.5)
Slack workspace already has Cursor installed (Cloud Agents / @cursor still works)
A recent change had the Cursor Slack app request two permissions that aren’t approved on our Slack Marketplace listing yet, so Slack blocks the install. We’ve let the team know and this is an issue we’re tracking.
In the meantime: existing Slack connections keep working, so hold off on disconnecting or clearing your Slack tokens - reconnecting is the part that’s currently blocked. A Slack-admin approval won’t fix it either. I’ll post here as soon as new installs work again.
Quick update: new Slack installs are working again!
If you were hitting the “Unapproved permissions requested” error, please retry — clicking Connect on the cursor.com integrations page or Add to Slack from the Slack Marketplace should now complete normally.
This also unblocks new Slack connections from the IDE. Thanks for the reports, and sorry for the disruption!
Hi — I’m hitting a Slack connection failure that looks different from the “Unapproved permissions requested” issue in this thread. It may also be a broader web/dashboard problem, not Slack-specific.
What I’m trying to do
On a Cursor Automation, Send to Slack shows Requires connection. I click Connect.
What happens
I’m redirected to https://cursor.com/dashboard/integrations, and the page fails with a generic error (Japanese UI):
何らかの問題が発生しました
予期せぬエラーが発生しました。もう一度お試しください。
(“Something went wrong / An unexpected error occurred. Please try again.”)
I never reach Slack’s OAuth / permission consent screen, so this does not appear to be the links:read, links:write install rejection.
Additional context
Logging into Cursor in the browser (not only Integrations) shows the same generic error page. So Connect → Integrations may be failing because the web app / dashboard itself is erroring, rather than because Slack OAuth is rejecting scopes.
Notes
Other tools on the same automation can connect; only Send to Slack stays on “Requires connection”.
The warning “One or more tools require additional authentication to be used” remains.
Retrying still shows the same crash.
I’m not attaching screenshots because the automation screen contains private workspace details.
Ask
Could you check whether the browser dashboard / integrations page is failing for some accounts, which would also block new Slack connections?
