Slack MCP auth fails with Must use PKCE to redirect to a non-web URI

I am also experiencing the same issue on the latest versions of everything.

I tried it again today and it seems to work, at least the error previously seen is not there. Since I am on a admin managed org slack, I’m awaiting the app installation.

I’m curious on the permissions though. Previously, cursor slack bot that can be requested from https://cursor.com/dashboard/integrations#integrations had different permissions some of which have been removed in the new slack bot installation from the slack mcp installation method.

This has been fixed. Thank you Cursor team!

Glad to hear it’s working, @Gaurav_Kumar

Regarding the permissions difference between the dashboard integration and the MCP plugin: the MCP server authenticates directly with Slack’s OAuth and requests its own scope set, which may differ from the legacy dashboard integration. The MCP scopes are tailored to what the agent needs for reading and searching messages.

If anyone else in this thread is still experiencing issues, please update to the latest version, run Clear All MCP Tokens from the command palette, restart Cursor, and try again.