Cursor Rules
Cursor Marketplace and Plugins
Cursor's marketplace is where you install plugins that extend the agent. A single plugin can bundle all six customization types at once: rules, skills, sub-agents, commands, MCP servers and hooks. Third-party plugins are reviewed by Cursor, and organisations can publish their own private catalogue for internal distribution.
On this page
What is the Cursor marketplace?
The marketplace is the install surface for everything that customises Cursor. Instead of hand-copying a rule file or wiring an MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. server by hand, you browse, install with a click, and the plugin's pieces land in the right places.
- Rules - conventions the agent follows.
- Skills - packaged know-how the agent loads when relevant.
- Sub-agents - roles that run in parallel.
- Commands - slash-menu jobs.
- MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. servers - connections to outside systems.
- Hooks - scripts that fire at lifecycle points.
What can a single plugin contain?
A plugin is a bundle. One install can ship any mix of the six customization types, so a team's whole working setup, rules plus skills plus the commands and MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. connections they depend on, travels as a single unit.
You can open and inspect a plugin's rules, skills, commands and hooks before trusting them, which makes the marketplace a good place to learn from well-written examples. Named community bundles like "superpowers" and "Continual Learning" are worth reading even if you don't install them.
Are marketplace plugins safe to install?
Third-party plugins are reviewed by Cursor before they're listed, and because most of a plugin is plain text you can read, you can audit what it does before installing. The exception is an MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. server, which is code that runs and reaches external systems, so review what it connects to and what permissions it asks for.
Treat an MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. server in a plugin like any other integration: confirm which systems it talks to and prefer least-privilege access (for example a read-only database connection) before you approve it.
How do teams distribute their own plugins?
Organisations can run a private marketplace: you publish an internal catalogue from an uploaded manifest, and developers install the team's approved rules, skills, commands, MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. servers and hooks from one place. Configuration distributes at three scopes - per user, per repository, and across the whole team - so admins can standardise once and let individuals add their own on top.
Plugins reach people through two kinds of marketplace. The first-party marketplace is the public catalogue Cursor lists; a private team marketplace is one your organisation runs for internal use. Both are GitHub-backed: the catalogue is a repository, so distributing a plugin and updating it is a normal pull-and-merge workflow rather than a separate publishing console.
- User
- Personal rules, skills and commands that travel with you.
- Repository
- Committed config every collaborator on the repo inherits.
- Team
- Centrally pushed catalogue and defaults for the whole organisation.
Standardise at the team scope; let people extend at the user scope.
Frequently asked questions
What can a Cursor plugin contain?
Any mix of the six customization types: rules, skills, sub-agents, commands, MCP servers and hooks. One install can set up a team's entire working configuration.
Are third-party plugins reviewed?
Yes. Cursor reviews third-party plugins before listing them, and because most of a plugin is readable text you can inspect rules, skills, commands and hooks yourself before installing.
Can I publish a private plugin for my team?
Yes. Organisations can publish an internal catalogue from an uploaded manifest so developers install the team's approved configuration from one place.
Sources & last verified
Cursor ships frequently. Facts verified against primary sources on June 25, 2026.