After Cursor’s recent Customize UI rollout, workspace-level MCP servers written to .cursor/mcp.json no longer appear under Customize → MCPs.
The configuration is valid and works when moved to the user-level ~/.cursor/mcp.json, suggesting the MCP server and endpoint are not the problem.
Steps to Reproduce
Open a project in Cursor.
Create /.cursor/mcp.json with a valid remote HTTP MCP server.
Open Customize → MCPs and select the workspace scope.
Run Developer: Reload Window.
Fully quit and reopen Cursor.
Check Customize and the Agent’s available tools.
Expected Behavior
Cursor should detect a valid .cursor/mcp.json for the open workspace and display the server under Customize → MCPs → Workspace without requiring users to modify their global configuration.
Thanks for the detailed report. Your MCP configuration is valid, and this is an issue we’re tracking.
Cursor 3.12.30 predates updates that restored workspace-level MCP handling in Customize. Please update to the latest stable version, then reopen the project.
If you use a multi-root .code-workspace, open the affected repository directly with File > Open Folder as a workaround. Its project MCPs should then appear under Customize > MCPs.
Hi @Siddhanth_Shetty — this is fixed for a single-folder project. Workspace MCP servers in .cursor/mcp.json were not showing under Customize after the recent UI change, and that handling is in the latest stable release. Please update, then reopen the project and check Customize → MCPs under the workspace scope.
@Kerkuil the multi-root .code-workspace case is also fixed, but that change has not rolled out to stable yet. It will land in an upcoming update, and I’ll post here when it’s out. If either of you still sees this after updating (or after that update lands, for multi-root), reply here, and we’ll dig back in. Thanks for the reports.