Plugins package skills, subagents, MCP servers, hooks, and rules into a single install. Browse plugins at https://cursor.com/marketplace or install directly in the editor with /add-plugin!
Our initial partners include Amplitude, AWS, Figma, Linear, Stripe, and more, covering workflows across design, databases, payments, analytics, and deployment. If your team already uses these tools, plugins give agents native access to them without writing custom skills from scratch.
Which plugins are you most excited to try, and what integrations are you hoping to see next?
How does the install experience feel?
If you’re a tool author, are you interested in building plugins for the Marketplace?
If you’ve found a bug, please post it in Bug Reports instead, so we can track and address it properly, but also feel free to drop a link to it in this thread for visibility.
This is really exciting. Very much looking forward to the private team marketplaces mentioned in “Coming soon” too! That’ll help us easily co-develop agent capabilities within a team to accelerate development in a specific context, and doing that with even other tool users (eg. Claude Code).
Is there a way to use plugins with the Cursor Cloud agent? On the documentation here: Plugins | Cursor Docs it says “They work across the IDE, CLI, and Cloud.” but I tried installing the Slack plugin and it doesn’t seem that the cloud agent has access to it.
As a developer I do really want to develop a plugin. My only question is, as the guy said above, how do we develop it locally so I can test it as the actual plugin and not just like rules and all, or do those work identically?
I just built out an MCP for my niche so this is the perfect next step, especially with the rules and sub-agents being able to all be bundled in one
It looks like a big oportunity so far, i’m very interested i how this will evolve in the future.
One thing i find confusing is the skills, rules etc. shown in the cursor settings tab. it doesn’t tell me where these originate from when i’m in the ‘all’ view.
it would be nice to see if, for example, a skill is sourced from a plugin and which plugin it’s from. makes managing them in combination with project and user documents easier.
In the comment I spot a motive of “requesting support for internal/custom plugins”
I wish to flag that, as our org have a private repo for centralizing plugins and skills, and it’s supported by claude code via `/plugin marketplace add myOwner/myRepo` even though it’s a private repo (uses my authorized gh cli, locally)
I wish to support that in cursor as well, so we can install and manage internal plugins, natively, without .sh copy-paste scripts
