When you moved the MCP configuration away from its usual location you also did the following:
Made it harder to find for people that don’t want to use agents view. Yes I know you can do “ctrl+shift-p mcp”, but that was not obvious.
The “one tool per line” view makes it harder to see all tools. This is not great, cause I have a server with 53 tools.
And this is the worst part - Tools no longer show descriptions or input params forcing me to use `mcp-inspector` along with Cursor.
Honestly, you are lucky that I’m specifically working on a project to make a custom MCP server + OAuth + Cursor work. If not for that I would immediately switch to a competitor. That said, if this will not be fixed in the near future I will do exactly that.
Hi @Ulf_Byskov Thank you for the post. And @Tien_Dat_Nguyen, thanks for your comment. I’m sorry for the hassle here. Customize is part of a broader effort to bring MCPs, plugins, rules, skills, and hooks into one place as Cursor evolves.
We appreciate you sharing your feedback. In the meantime, Ctrl/Cmd+Shift+P → Open MCPs is the quickest direct route. That is not a substitute for making the UI easier to find, but it should reduce the navigation.
But seriously, judging from the feedback I have seen recently, the way you have envisioned centralising things in the Agents window is clearly not aligned with what people want. Most developers still want a file tree and a proper editor and do not jump between agent sessions but work in a linear process one LLM interaction at a time.
Personally, I believe that despite the new agents/customize view, you should have left the MCP configuration as it was in the VS Code editor. At a minimum, you could have added a way to open “customize” from the regular Cursor settings.