Feature request for product/service
Cursor IDE
Describe the request
Cursor currently imports third-party plugins/configs from other tools, including Claude Code, through:
Settings → Rules, Skills, Subagents → Include third-party Plugins, Skills, and other configs
This setting appears to be all-or-nothing. When enabled, Cursor imports third-party plugins, skills, rules/configs, and MCP servers. When disabled, Cursor disables all third-party imported content.
This creates a problem for plugins that bundle useful skills together with MCP servers.
What happened
I have several custom Claude Code plugins installed. Cursor automatically imports them as Imported plugins. These plugins include useful skills, but they also define MCP servers.
In Cursor:
Settings → Plugins shows various imported plugins.
Some of these show 1 skill, 1 MCP server; others show 1 MCP server.
Then in:
Settings → Tools & MCPs → Plugin MCP Servers
Cursor lists the MCP servers from those imported plugins. Even when the MCP servers are disabled, they remain present as plugin-provided MCPs.
More importantly, the MCPs will become re-enabled when I switch worker nodes on the HPC that I’m remotely connected to. I then get bombarded with Oauth workflow prompts to authorize each MCP in each Cursor session that I have open.
Expected behavior
Cursor should provide granular control over third-party imports, for example:
- Import third-party skills: on/off
- Import third-party rules/configs: on/off
- Import third-party MCP servers: on/off
Or, at minimum, each imported plugin should allow disabling only its MCP server contribution while preserving its skills/rules.
Actual behavior
The only global control I can find is:
Include third-party Plugins, Skills, and other configs
Turning this off disables all imported third-party content, including useful skills. Leaving it on imports MCP servers as well.
The plugin detail page has an Uninstall button, but clicking it redirects to Rules, Skills, Subagents rather than uninstalling the imported plugin. I understand this may be intentional for imported plugins, but it means there is no way to remove or suppress only the MCP portion of an imported plugin.
Why this matters
Many Claude Code plugins bundle skills and MCP definitions together. In Cursor, I want to keep using the imported skills, but I do not want Cursor to import or initialize the MCP servers.
In my case, the MCP servers require OAuth. Cursor repeatedly prompts me to complete the OAuth flow for MCPs that I do not want to use in Cursor. Disabling all third-party plugin import avoids the prompts, but also removes the imported skills I do want.
Requested change
Please add one of the following:
- A global setting to disable importing third-party MCP servers while keeping third-party skills/rules enabled.
- A per-plugin setting to disable MCP contributions from an imported plugin.
- A per-MCP “hide/remove from Cursor” option for plugin-provided MCP servers.
- A way for imported plugin uninstall/disable to affect only Cursor without requiring all third-party imports to be disabled.
Current workaround
The only reliable workaround appears to be disabling:
Rules, Skills, Subagents → Include third-party Plugins, Skills, and other configs
But that disables all imported third-party plugins/skills/configs, which is too broad.
Operating System (if it applies)
Linux