Cursor Rules
Cursor Marketplace and Plugins
Cursor Marketplace is where you install plugins that extend the agent. A plugin can bundle rules, skills, sub-agents, commands, MCP servers and hooks. Official Google Workspace plugins connect Gmail, Drive and Calendar as separate installs, and team marketplaces distribute approved internal plugins to the people who need them.

On this page
What is the Cursor marketplace?
The marketplace is where you install plugins that customize Cursor. Instead of copying a rule file or wiring up an MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. server by hand, you browse, install with one click, and the pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition.'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.
- MCP servers
- Connections to outside systems.
- Hooks
- Scripts that fire at lifecycle points.
The marketplace and the extension registry are separate catalogs, and they are easy to confuse. Editor extensions and themes still come from Open VSX (migrating from VS Code covers what that changes). The marketplace installs agent configuration: MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. servers, skill files and config, so one click can bring in more than it appears to.
This exact topic is a hands-on Lesson: Use Google Workspace plugins — about 8 minutes, free to read.
Rather do it than read about it? Run 11 interactive Cursor walkthroughs in a simulated editor. Free, no account needed.
What can a single plugin contain?
A pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. is a bundle. One install can ship any mix of the six customization types, so a team's whole working setup travels as a single unit: rules, skills, and 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. Press Enter for the full definition. connections they depend on.
If the six-type list feels abstract, here's the field shorthand for what most plugins actually are.
A pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. is basically MCPs and skills put together. Sometimes you'll see some sub-agents and hooks in there, but for the most part it's just a combination of MCPs and skills.
You can open and inspect a pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition.'s rules, skills, commands and hooks before you trust them, which makes the marketplace a good place to learn from well-written examples. Superpowers, a community skills library, and Cursor's own Continual Learning plugin are worth reading even if you don't install them.
What are some real plugins worth knowing?
The catalog is easier to grasp through named examples than through the six-type list. A few are first-party or Cursor-authored, which makes them good reference material as well as useful installs.
The Figma team approached Cursor to publish this one, so designers working inside Cursor get a first-class experience. Its skills turn designs into code, push UI back to Figma, build a design-system library in Figma from your code, and create Design, FigJam and Slides files. It's a named first-party integration, not a community MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition..
Cursor open-sources its own internal sub-agents, skills and rules as a pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. you can search for by name. It shows how Cursor's engineers write short rules and structure their skills and sub-agents, so it is a starting point you can copy if you're unsure how to shape your own primitives.
Plugins also do useful plumbing. A custom IDE pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. can wire in the MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. client definitions for a set of servers, then ship skills that steer the agent to use those MCP tools well. One install gets you the servers and the skills that know how to drive them.
The Google Workspace release is a concrete case: Cursor lists separate Google Drive, Gmail and Google Calendar plugins in Marketplace and Customize.
Drive can search, open, create and organize files, and Gmail can read, draft and send mail or manage threads. Calendar can read schedules, find free time and change events. Install only the account access a workflow needs, and see the Google Workspace pluginsSeparate Cursor plugins for Gmail, Google Drive and Google Calendar that let an authorized agent read or change workspace data. Press Enter for the full definition. guide for the action boundaries.
This IntelliJ pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. wires in the MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. client definitions for the servers we just added automatically. And then it also has a bunch of skills that I added that help steer and guide Cursor to use those MCP tools effectively.
Not every connector is built into Cursor, but many install in one click: open Customize, choose MCPs, and click Add to Cursor next to the server. For Jira and Confluence, the Cursor Marketplace lists an Atlassian pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. that bundles an MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. server and skills for both. Once it is connected, you can query those knowledge bases from Ask modeA read-only mode for asking questions about a codebase without changing files; the safe way to explore unfamiliar or legacy code. Press Enter for the full definition..
Are marketplace plugins safe to install?
Cursor reviews third-party plugins before it lists them, and because most of a pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. is plain text, you can audit what it does before you install it. 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. Press Enter for the full definition. server, which is code that runs and reaches external systems. 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. Press Enter for the full definition. server in a pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. 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.
That leaves hooks. They sit in the readable half of the bundle, which makes them easy to skip past. A command hook, the default kind, is a shell script Cursor runs when the agent hits a lifecycle point, so installing a bundle that ships one means agreeing to run someone else's script at that point.
Reading a pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. is a good way to learn from it, but we wouldn't count it as a review. The hook and the server are what change your exposure.
How do teams distribute their own plugins?
On Teams and Enterprise plans, an organization can run its own team marketplace. Admins create one from scratch or import it from a repository, 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. Press Enter for the full definition. servers and hooks from one place.
Plugins reach people through two kinds of marketplace: the public Cursor Marketplace and your team's own. A team marketplace imported from a repository stays tied to it, so you add or update a pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. with a commit, not in a separate publishing console. The marketplace picks up the change when it refreshes, which can happen automatically on a GitHub import.
- User
- Personal rules, skills and commands that travel with you.
- Repository
- Committed config every collaborator on the repo inherits.
- Team
- A centrally pushed catalog and defaults for the whole organization.
Standardize at the team scope; let people extend at the user scope.
Which scope to standardize at is mostly a question of headcount. For a handful of people, committed repo config covers it, and a team marketplace is machinery you would maintain for its own sake. It is worth the upkeep once asking everyone to set up the same thing stops working. Even then, push team-wide only what causes a problem when it differs between people, and leave preferences at user scope.
Some governance needs have no built-in feature, and that is where your own pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. pays off. Take App Store and Play Store rules on code transparency, user safety and native permissions. A plugin of skills and rules can guide the agent to follow those policies and check the code as it is written. Encoding them still takes real work, but the result is a check you can reuse and distribute instead of a manual review.
Members on Teams and Enterprise plans can publish a personal skill to the team's Default marketplace. Beyond your team, you can submit a pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. to the public Cursor Marketplace for review. Cursor keeps it curated, working directly with authors it trusts, and plans to open listing up more broadly as its vetting matures.
How do Customize and deeplinks fit into plugin rollout?
The Customize page is where you install and manage plugins, skills and MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. servers. Deeplinks are the sharing layer: a team can hand someone a link to a prompt, command or rule that opens in Cursor or through cursor.com.
Use Customize for lasting installs, and deeplinks to share one working pattern.
- Surface
- Customize
- Use it for
- Adding and managing plugins, skills and MCPs at user, team or workspace scope.
- Surface
- Plugins
- Use it for
- Packaging rules, skills, agents, commands, MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. servers and hooks into one distributable bundle.
- Surface
- Deeplinks
- Use it for
- Sharing prompts, commands and rules so another developer can open the same workflow quickly.
| Surface | Use it for |
|---|---|
| Customize | Adding and managing plugins, skills and MCPs at user, team or workspace scope. |
| Plugins | Packaging rules, skills, agents, commands, MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. servers and hooks into one distributable bundle. |
| Deeplinks | Sharing prompts, commands and rules so another developer can open the same workflow quickly. |
Customize is where the bundle lands; deeplinks are how a specific workflow travels.
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. In practice most plugins combine MCP servers and skills, sometimes with a few sub-agents and hooks.
Are there any first-party or Cursor-authored plugins?
Yes. The Figma plugin is created by Figma and verified by Cursor, with skills for turning designs into code and building design-system libraries. Cursor also open-sources its own sub-agents, skills and rules as the Cursor Team Kit plugin, which doubles as a reference for writing your own primitives.
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 its rules, skills, commands and hooks yourself before installing.
Does one Marketplace plugin connect all of Google Workspace?
No. Google Drive, Gmail and Google Calendar are separate plugins, so install only the app access a workflow needs. The dedicated Google Workspace plugins guide covers setup, connected-account checks and action boundaries.
Can I publish a private plugin for my team?
Yes, on Teams and Enterprise plans. Admins create a team marketplace from scratch or import one from a repository, and developers install the team's approved plugins from one place.
Sources & last verified
- Cursor Customize
- Cursor Plugins
- Cursor Changelog - Google Workspace Plugins
- Cursor Deeplinks
- Cursor - Learn
- Cursor Marketplace
- Cursor Help: Marketplace security
- Cursor Help: MCP integrations
Cursor ships frequently. Facts verified against primary sources on August 14, 2026.