Can't Add Private Marketplace with Team License

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After deleting our private marketplace in the Cursor UI, with the intent to replace it with a different marketplace repo we built, we see an error message stating “Upgrade to Enterprise to import more team marketplaces”, preventing us from adding our one private marketplace repo allowed by our Teams license.

We now see only the “Default” marketplace which can’t be deleted.
All workflows and automations that relied on our custom plugins are no longer working because our private marketplace has been deleted and the Cursor UI is not allowing us to add the private marketplace again.

Our Cursor workflows (e.g. Automations) are effectively unusable until our plugin marketplace is fixed.

Steps to Reproduce

Setup: Have Cursor Teams license.

  1. Navigate to cursor.com/agents, open settings, then click “Plugins” for plugin settings
  2. Add a private marketplace - should have “default” and your custom marketplace visible
  3. Delete the private marketplace
  4. Add a marketplace again via “Add Marketplace” button
    EXPECTED: Should be able to add a private marketplace again
    ACTUAL: Receive error stating “Upgrade to Enterprise to import more team marketplaces” when we have zero private marketplaces configured with a Teams license

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Performed via https://cursor.com/dashboard/plugins on 8/17 @ 3pm CT

Does this stop you from using Cursor

Yes - Cursor is unusable

Hi @menotcomputer Thanks for the post. You shouldn’t be seeing that, and it isn’t caused by anything in your setup. On Teams you can import one team marketplace. Default is a built-in marketplace (it isn’t deletable), and it currently counts toward that limit. After you removed your imported marketplace, Add Marketplace stays disabled with the Enterprise upgrade message, even though you have no imported marketplace left. That isn’t intended behavior. We’ve let the team know, and this is an issue we’re tracking. No timeline to share yet, but I’ll post here when there’s an update.

There isn’t a dashboard path to import a replacement team marketplace while Default is still counting toward the limit, so team-shared Automations that depended on those plugins can’t be restored from Plugins settings right now.

If people need the plugins in the editor in the meantime, you can load them locally on each machine. That path is per-user and will not restore team-shared Automations: https://cursor.com/docs/plugins#test-plugins-locally

Will keep you posted with any relevant updates here.

Hi @kevinn - Thank you for your response.
The private plugin marketplace is a paid feature that is not functional for our organization, and is currently preventing us from using Cursor Automations (via Cloud Agents) that many of our workflows are reliant on. It would not be an insignificant amount of work to migrate away from Cursor Automations which aren’t currently functional without the custom plugins hosted in our private marketplace.

I don’t believe that “installing the plugins locally” is a viable path forward for us.
Is there anything else you can do to help resolve this issue ASAP?

Hi @menotcomputer I don’t have ETA but the right eyes are on it and we’ll let you know any relevant updates

Same issue on our Teams plan — adding our vote / another reproduction.

Setup

  • Plan: Teams
  • Dashboard → Plugins shows only the built-in Default marketplace (__DEFAULT__)
  • Contents: 0 plugins
  • Add Marketplace is blocked / directs us to upgrade to Enterprise for more team marketplaces
  • Delete Marketplace looks enabled on Default; we have not deleted it (system-owned + don’t want to break Team MCP linkage)

What we’re trying to do Import one private Team Marketplace (plugins/skills) from a Bitbucket repo, which 3.9 says is supported: Customize Cursor · Cursor

Expected: Teams gets Default (for Team MCP distribution) plus one imported marketplace. Default should not consume the Teams slot.

Actual: Default fills the only slot, so we cannot import our marketplace at all. Matches Kevin’s note above that Default currently counting toward the limit is unintended.

Happy to share team ID / screenshots privately if that helps. Any update on a fix or a temporary override for Teams orgs stuck on Default-only?

Bump