# NightlyCursor+Slack MCP plugin still does not work

**URL:** <https://forum.cursor.com/t/nightlycursor-slack-mcp-plugin-still-does-not-work/163261>\
**Category:** Bug Reports\
**Tags:** plugins, mcp, slack, nightly\
**Created:** [June 14, 2026, 6:11pm UTC](https://forum.cursor.com/t/nightlycursor-slack-mcp-plugin-still-does-not-work/163261 "2026-06-14T18:11:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eugen\_Konkov](https://avatars.discourse-cdn.com/v4/letter/e/e274bd/32.png) [@Eugen\_Konkov](https://forum.cursor.com/u/Eugen_Konkov)\
**Post date:** [June 14, 2026, 6:11pm UTC](https://forum.cursor.com/t/nightlycursor-slack-mcp-plugin-still-does-not-work/163261/1 "2026-06-14T18:11:22Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

It is already  
Version: 3.7.39  
but you still have not fixed this problem. [Slack integration does not work with cursor-nightly - #20 by Eugen\_Konkov](https://forum.cursor.com/t/slack-integration-does-not-work-with-cursor-nightly/155872/20)

### Steps to Reproduce

1. Try to connect Slack MCP Plugin with CursorNightly

### Operating System

MacOS

### Version Information

Version: 3.7.39  
VS Code Extension API: 1.105.1  
Commit: 142089e1157f04e847f3960d82a9a8d61d25f7c9  
Date: 2026-06-14T01:39:43.144Z  
Layout: editor  
Build Type: Nightly  
Release Track: Nightly  
Electron: 39.8.1  
Chromium: 142.0.7444.265  
Node.js: 22.22.1  
V8: 14.2.231.22-electron.0  
xterm.js: 6.1.0-beta.256  
OS: Darwin arm64 25.3.0

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![Eugen\_Konkov](https://avatars.discourse-cdn.com/v4/letter/e/e274bd/32.png) [@Eugen\_Konkov](https://forum.cursor.com/u/Eugen_Konkov)\
**Post date:** [June 14, 2026, 11:28pm UTC](https://forum.cursor.com/t/nightlycursor-slack-mcp-plugin-still-does-not-work/163261/5 "2026-06-14T23:28:37Z")

</div>

I want to note, that Atlassian MCP connection works well. It redirects to the correct page and authenticate.

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [June 15, 2026, 9:26am UTC](https://forum.cursor.com/t/nightlycursor-slack-mcp-plugin-still-does-not-work/163261/7 "2026-06-15T09:26:16Z")

</div>

You’re right that it isn’t fixed yet for the standalone Cursor Nightly app, and your Atlassian observation is a useful clue. Different MCP providers register their OAuth callbacks differently. Atlassian’s setup accepts the standalone Nightly app’s callback, but Slack’s OAuth configuration currently only accepts the regular Cursor app’s callback scheme, so Slack MCP auth fails specifically on the standalone Nightly download. This is a known limitation on our side, and we’re working on a change to the connection flow that will fix it for the standalone app.

In the meantime, the reliable workaround is to run the regular Cursor app on the Nightly channel instead of the separate Nightly download:

1. Install the standard Cursor app from [Cursor · Download](http://cursor.com/download)
2. Open Cursor Settings → Beta → Update Access and select Nightly

You’ll still get nightly builds, but since it’s the regular app it uses the callback scheme Slack accepts, so Slack MCP connects normally.

One note since it came up before: your standalone Nightly app keeps its own separate settings, so doing this won’t delete or overwrite any of your existing Nightly configuration.

I’ll update this thread once the fix for the standalone app ships.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [July 15, 2026, 9:26am UTC](https://forum.cursor.com/t/nightlycursor-slack-mcp-plugin-still-does-not-work/163261/8 "2026-07-15T09:26:44Z")

</div>

Closed on July 15, 2026, 9:26am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
