# New Customize area broken for workspace-level MCPs **URL:** \ **Category:** Bug Reports\ **Tags:** mcp\ **Created:** [August 6, 2026, 4:43pm UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625 "2026-08-06T16:43:18Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Noland](https://avatars.discourse-cdn.com/v4/letter/n/eb8c5e/32.png) [@Noland](https://forum.cursor.com/u/Noland)\ **Post date:** [August 6, 2026, 4:43pm UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/1 "2026-08-06T16:43:18Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug I have lots of working MCP servers defined in my project’s `mcp.json` file but when I go to Cursor Settings → Customize → select repo within project → MCPs, the list is empty, no servers shown. I can’t see their status, can’t enable/disable them, and I can’t configure which tools are enabled/disabled. When I click on the “+New” button, it opens my `mcp.json` file and all my servers are there. And they work. ### Steps to Reproduce Make a multi-root workspace and add an `mcp.json` file. ### Expected Behavior All my custom MCP servers show up in the workspace level area and I can see their status and enable/disable them and their tools. ### Screenshots / Screen Recordings ![Desktop-screenshot-08-06-2026_09_38_AM.png](https://us1.discourse-cdn.com/cursor1/original/3X/0/b/0b2efa46d0c6f76619a97b0518f2e367959d2256.png) ### Operating System Linux ### Version Information Version: 3.14.27 VS Code Extension API: 1.128.0 Commit: 047548b00c1a079373d74d00183f32510a4a41e0 Date: 2026-08-04T03:29:11.183Z Layout: IDE Build Type: Stable Release Track: Default Electron: 40.10.3 Chromium: 144.0.7559.236 Node.js: 24.15.0 V8: 14.4.258.32-electron.0 xterm.js: 6.1.0-beta.291 OS: Linux x64 6.8.0-71-generic ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![Mitch\_OM](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mitch_om/32/88895_2.png) [@Mitch\_OM](https://forum.cursor.com/u/Mitch_OM)\ **Post date:** [August 6, 2026, 6:20pm UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/5 "2026-08-06T18:20:16Z")
Also can’t see my workspace mcp. this tabbed view is much worse. Seems like some design philosophy keeps pushing the ui to be compartmentalized in a way that’s much much worse than before. Please stop it. ---
**Author:** ![Matt\_Marion](https://avatars.discourse-cdn.com/v4/letter/m/ee59a6/32.png) [@Matt\_Marion](https://forum.cursor.com/u/Matt_Marion)\ **Post date:** [August 6, 2026, 8:28pm UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/7 "2026-08-06T20:28:27Z")
Same issue. Driving me nuts. Yesterday I was able to just go into settings and enable/disable my project level mcps. Now that’s apparently gone and there’s a “Customize” section. Except it’s for team, users, etc. My MCP’s are setup on a project by project basis, not on a user or team basis. They are often specific to projects (like test devices). Anyone have any idea why they are doing this? What was broken that they are trying to fix and is there an official way to get them to look at it? I need my MCP’s running ☹ Edit: After typing this I went back in clicked on my username and I had workspace ones there. Seems to be working again. ---
**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:** [August 7, 2026, 10:13am UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/9 "2026-08-07T10:13:35Z")
Hey there! Nothing’s wrong with your config, and those servers are still loaded and working. What you’re hitting is a scoping issue in the new Customize area specific to multi-root workspaces (a `.code-workspace` with more than one folder). It’s not intended behavior, and it’s an issue we’re tracking. In the meantime, open the repo on its own (File → Open Folder → the repo root). In a single-folder window, Customize → MCPs lists that repo’s servers with status and enable/disable toggles. You can also keep editing them directly in `.cursor/mcp.json` (what “+ New” opens). I’ll post back here when there’s an update. ---
**Author:** ![GetoX](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/getox/32/116576_2.png) [@GetoX](https://forum.cursor.com/u/GetoX)\ **Post date:** [August 11, 2026, 7:50am UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/10 "2026-08-11T07:50:26Z")
Five days and this issue is still open. I have so many problems with the multi-root workspace in Cursor that I think the company is trying to push me towards competing solutions. ---
**Author:** ![Kazopl](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kazopl/32/90359_2.png) [@Kazopl](https://forum.cursor.com/u/Kazopl)\ **Post date:** [August 13, 2026, 8:11am UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/13 "2026-08-13T08:11:48Z")
@mohitjain still reproducing on 3.16.13 Nightly (Aug 13 build), macOS arm64. My setup: multi-root workspace with 4 folders. 2 user servers in `~/.cursor/mcp.json`, 10 project servers across three of the folders (1 + 5 + 4). Customize \> MCPs shows “Connected 2” with only the user servers, under every scope in the dropdown. The project servers are connected and the agent calls their tools fine, so it’s only the UI. One detail I haven’t seen in this thread yet: the scope dropdown itself is incomplete. It offers only 2 of my 4 folders. The folder with the most config (4 MCP servers plus rules and skills) never appears as an option at all, so even the “select the owning folder” path is dead for it. It’s not just server rows being filtered out, folders are missing from the scope picker too. Version: 3.16.13 VS Code Extension API: 1.128.0 Commit: ea1aa2c63ff7f41a377f250d1c8fd7dd2230e280 Date: 2026-08-13T01:59:26.203Z Layout: IDE Build Type: Stable Release Track: Nightly Electron: 40.10.3 Chromium: 144.0.7559.236 Node.js: 24.15.0 V8: 14.4.258.32-electron.0 xterm.js: 6.1.0-beta.291 OS: Darwin arm64 25.6.0 ---
**Author:** ![puroman](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/puroman/32/19944_2.png) [@puroman](https://forum.cursor.com/u/puroman)\ **Post date:** [August 13, 2026, 4:47pm UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/14 "2026-08-13T16:47:52Z")
same issue ---
**Author:** ![Cios\_Ka](https://avatars.discourse-cdn.com/v4/letter/c/77aa72/32.png) [@Cios\_Ka](https://forum.cursor.com/u/Cios_Ka)\ **Post date:** [August 13, 2026, 5:29pm UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/15 "2026-08-13T17:29:31Z")
This is quite a bad regression, imho. MCP servers are core to the whole Cursor experience. Not testing how this new setup works in multi-root workspaces is not a great look. > Nothing’s wrong with your config, and those servers are still loaded and working This is false. My agent reports that it sees no MCP servers. This is in version 3.15.19. … Just tested with Nightly (3.16.13). At least that version uses the project MCP servers again, even though the UI still doesn’t show them. ---
**Author:** ![A\_A6](https://avatars.discourse-cdn.com/v4/letter/a/cab0a1/32.png) [@A\_A6](https://forum.cursor.com/u/A_A6)\ **Post date:** [August 14, 2026, 12:57am UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/17 "2026-08-14T00:57:36Z")
This is much much worse: it literally blocks all MCP usage in Cursor. All our MCPs require authentication - this is obvious, since MCPs are handling critical data. The new system makes it literally impsosible to authenticate any MCP server - you removed the UI that would show a button ‘authenticate’. There is no workaround as far as I can see. ---
**Author:** ![Andrey\_Tepaykin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/andrey_tepaykin/32/117846_2.png) [@Andrey\_Tepaykin](https://forum.cursor.com/u/Andrey_Tepaykin)\ **Post date:** [August 17, 2026, 3:37pm UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/18 "2026-08-17T15:37:45Z")
Cursor repeatedly tries to connect to a local SSE MCP while the extension is still indexing (~240s), then marks the server as failed (“tool discovery” error) and stops retrying. After that, the MCP backend is healthy and indexing completes, but Agent never gets the tools back. In past versions I could see MCPs status and could make `reload` on errored, but can’t do in new version. Environment OS: Windows 10 Cursor: Version: 3.16.17 Workspace: large monorepo Server: ECIP Local extension (naman09khater.ecip-local) ---
**Author:** ![Marco\_Araujo\_CU](https://avatars.discourse-cdn.com/v4/letter/m/c89c15/32.png) [@Marco\_Araujo\_CU](https://forum.cursor.com/u/Marco_Araujo_CU)\ **Post date:** [August 19, 2026, 9:59am UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/19 "2026-08-19T09:59:37Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug In a multi-root .code-workspace, Open Customize → MCPs only lists User servers. Project servers from a folder’s .cursor/mcp.json do not appear, so there is no enable/disable toggle and no OAuth / Authenticate control for them. The old Settings → Tools & MCP sidebar item is gone. The only path is Cmd+Shift+P → Open Customize → MCPs. Some project servers still connect in Agent. Remote OAuth project servers often do not load at all (missing from the agent catalog), so they cannot be turned on or authenticated from the multi-root workspace. Related: 167625, 167648, 167808. This report is macOS, Cursor 3.16.29. ### Steps to Reproduce Create a folder with .cursor/mcp.json that defines project MCP servers (local stdio and at least one remote URL / OAuth server). Create a multi-root .code-workspace that includes that folder plus at least one other folder. Open the .code-workspace in Cursor. Cmd+Shift+P, run Open Customize, then open the MCPs tab. Only User servers are listed. Project servers from .cursor/mcp.json are missing. There is no enable toggle or Authenticate control for them. In Agent, list connected MCP servers. Remote OAuth project servers are often missing from the catalog. File \> Open Folder on the folder that owns .cursor/mcp.json (single-folder window). Open Customize \> MCPs again. The project servers appear and can be toggled or authenticated. ### Expected Behavior Opening a multi-root .code-workspace should load project MCP servers from each folder’s .cursor/mcp.json, the same as File \> Open Folder on that repo. Open Customize \> MCPs should list those project servers with enable/disable and Authenticate / OAuth. Remote OAuth project servers should appear in the agent MCP catalog after they are enabled, without needing to leave the multi-root workspace. ### Operating System MacOS ### Version Information Cursor IDE: 3.16.29 (stable) Commit: 6246455961129c32969845e00aa25d87ae926ec0 Layout: IDE Build type: Stable OS: macOS 26.5.2 (darwin 25.5.0), arm64 ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![JD\_1](https://avatars.discourse-cdn.com/v4/letter/j/3da27b/32.png) [@JD\_1](https://forum.cursor.com/u/JD_1)\ **Post date:** [August 20, 2026, 11:23am UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/22 "2026-08-20T11:23:23Z")
Same here on **3.16.29 (macOS, stable)**. Adding data rather than another +1, because in my setup this isn’t cosmetic — the servers genuinely don’t connect. **Setup:** one `.code-workspace` with ~30 folders. Five of them ship a `.cursor/mcp.json` defining a remote MCP server. Same URL for all five, but each sends a **different `Authorization` header** , because each repo maps to a different project in the upstream service. **What actually loads:** | Workspace folder (index) | Visible in Customize | Agent can call tools | | --- | --- | --- | | 0 | yes | yes | | 15 | yes | yes | | 24 | no | no | | 25 | no | no | | 27 | no | no | All five files are the same shape, valid JSON, unique server names, no `${env:}` interpolation in the three broken ones. So it isn’t “first root only” — root 15 works fine while 24, 25 and 27 don’t. I can’t see a pattern that explains which ones survive. The scope dropdown in Customize → MCPs also lists fewer entries than I have folders, so I can’t even select the broken folders to inspect them. And because the row never renders, there’s no toggle and no Authenticate button to click — the usual “disable and re-enable it” advice has nothing to act on. **Why this breaks my workflow specifically** The per-folder scoping _is_ the feature. Each repo’s key grants write access to that repo’s project only. That’s deliberate: an agent working in one product repo must not be able to write into another product’s project. Repo-level rules and skills reference each server by name and say “never use the global one for this repo.” So the two suggested workarounds both fail for me: - **Move them to `~/.cursor/mcp.json`.** This hands every repo write access to all five projects at once and puts five near-identical tool sets in front of the agent, which then picks the wrong one. It converts a safety boundary into a coin flip. Not something I’m willing to ship to my team. - **Open each folder in its own window.** This is the actual workaround I’m using, and it means abandoning the multi-root workspace for exactly the tasks where I need it. Cross-repo work now needs two windows and a manual context switch. The net effect is that three of my five repos have silently lost their MCP tooling, and the failure mode is the bad kind: nothing errors, the tools are simply absent, so an agent following the repo’s own rules just reports the server isn’t configured. **What would help most** , roughly in order: 1. Make project servers connect in multi-root workspaces again, even if the Customize UI stays broken a bit longer. Working tools with no UI beats a UI with no tools. 2. Surface a load error somewhere reachable. If a folder’s `mcp.json` is skipped, MCP Logs should say which folder and why, instead of the entry vanishing. 3. Populate the scope dropdown from the workspace folder list, so a folder with a config can never be unselectable. Many thanks in advance for fixing this issue. ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [August 26, 2026, 12:58pm UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/23 "2026-08-26T12:58:18Z")
This issue should be fixed in _v3.17_! ---
**Author:** ![leandromsales](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/leandromsales/32/120786_2.png) [@leandromsales](https://forum.cursor.com/u/leandromsales)\ **Post date:** [September 14, 2026, 1:12am UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/24 "2026-09-14T01:12:01Z")
I am using 3.19.13 (Universal) and still have this exact issue. Is there any plan to fix it, which is essential for me and my team? ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [September 14, 2026, 9:18am UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/25 "2026-09-14T09:18:15Z")
@leandromsales It sounds like you might be encountering a different issue, can you please raise a new thread with more details? ---
**Author:** ![leandromsales](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/leandromsales/32/120786_2.png) [@leandromsales](https://forum.cursor.com/u/leandromsales)\ **Post date:** [September 24, 2026, 10:13pm UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/31 "2026-09-24T22:13:49Z")
@Colin no sir! It is exactly the same, as in the original post picture: ![Desktop-screenshot-08-06-2026_09_38_AM](https://us1.discourse-cdn.com/cursor1/original/3X/0/b/0b2efa46d0c6f76619a97b0518f2e367959d2256.png) ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [September 24, 2026, 11:20pm UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/38 "2026-09-24T23:20:36Z")
Hey @leandromsales, thanks for following up. That screenshot is the one from the original post, so I’d like to check what’s happening on your side. In a multi-folder workspace, Customize currently starts with only User and Team selected, so project MCP servers stay hidden until you pick a folder. That choice also resets each time you reopen Customize. Could you try this? 1. Open your workspace in Cursor the way you normally do. 2. Open the Command Palette (Cmd+Shift+P), run “Open Customize”, and click the MCPs tab. 3. Click the scope dropdown at the top left (it shows your name). 4. If the folder with your .cursor/mcp.json isn’t listed, click “N more” to expand the list. 5. Tick that folder. Do your project servers appear after step 5? If not, please reply with: - A screenshot of your own Customize \> MCPs page with the dropdown open - The full path to your mcp.json (is it directly inside a workspace folder, or in a subfolder like packages/app/.cursor/mcp.json?) - Whether you’re in the editor window or the Agents window ---
**Author:** ![leandromsales](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/leandromsales/32/120786_2.png) [@leandromsales](https://forum.cursor.com/u/leandromsales)\ **Post date:** [September 25, 2026, 2:58am UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/39 "2026-09-25T02:58:17Z")
@Colin, yes I used the original screenshot because it is the same case. And yes, after step 5 I could see the MCP entries from my project scope (.cursor/mcp.json in the same folder as the workspace definition file. Why doesn’t Cursor simply save my choices of step 5 in the project profile? ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [September 25, 2026, 4:53am UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/46 "2026-09-25T04:53:01Z")
Thanks for checking, @leandromsales, that’s helpful. That confirms it. What this thread was originally about was that project servers never showed up even with the folder selected, and that’s fixed in the version you’re on. What you’re seeing now looks the same, but it’s a separate behavior: in a multi-folder workspace, Customize starts with only User and Team selected, and it doesn’t remember your folder choice when you close and reopen it. I agree it should either include your workspace folders by default or remember your selection, and I’ve passed your report on to the team. In the meantime, ticking the folder in the scope dropdown is the way to see and manage those servers. They keep working in Agent either way. ---
**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:** [October 25, 2026, 4:53am UTC](https://forum.cursor.com/t/new-customize-area-broken-for-workspace-level-mcps/167625/47 "2026-10-25T04:53:25Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.