| [ Web Proxy ] |
| Viewing: https://cursor.com/docs/plugins | [Back] [Original] |
Search for a command to run...
Plugins package rules, skills, agents, commands, MCP servers, and hooks into distributable bundles.
Cursor supports the Agent Plugins open standard alongside its own plugin format. Install and manage them from the Customize page or browse official plugins in the Cursor Marketplace. For community plugins and MCP servers, browse cursor.directory. You can also build your own to share with other developers.
A plugin can bundle any combination of these components:
| Component | Available in | Description |
|---|---|---|
| Rules | Cursor Plugins | Persistent AI guidance and coding standards (.mdc files) |
| Skills | Both formats | Specialized agent capabilities for complex tasks |
| Agents | Cursor Plugins | Custom agent configurations and prompts |
| Commands | Cursor Plugins | Agent-executable command files |
| MCP Servers | Both formats | Model Context Protocol integrations |
| Hooks | Cursor Plugins | Automation scripts triggered by events |
Plugins bundle reusable components an agent can use. Agent Plugins is the open standard for packaging portable skills and MCP servers, much like Agent Skills defines a standard for individual skills. Cursor supports Agent Plugins alongside Cursor Plugins.
plugin.json manifest at the plugin root, packaging skills and MCP servers.cursor-plugin/plugin.json manifest, which add rules, agents, commands, hooks, and variablesA plugin that follows the Agent Plugins specification loads in Cursor without changes. Cursor Plugins continue to develop in parallel with the standard, so Cursor-specific components and marketplace features keep working as they do today.
Learn more at agent-plugins.org or read the specification on GitHub.
Plugins now ship with prebuilt canvases: shared setup templates your team can open and reuse.
Open a canvas from an installed plugin in Customize to get a guided starting point instead of configuring everything from scratch.
The Cursor Marketplace is where you discover and install official Cursor Plugins. Plugins are distributed as Git repositories and submitted through the Cursor team.
Every plugin is manually reviewed before it's listed. Browse official plugins at cursor.com/marketplace or search by keyword in Customize. For community plugins and MCP servers, browse cursor.directory.
Team marketplaces are available on Teams and Enterprise plans. They can distribute Agent Plugins and Cursor Plugins through the same marketplace.
Contact sales for unlimited team marketplaces and Enterprise admin controls.
Open Dashboard -> Plugins to manage Team Marketplaces.
On Enterprise plans, only admins can add team marketplaces from Dashboard -> Plugins.
The Default team marketplace connects shared plugins and MCP servers across Cursor. Admins can add Team MCP servers that are already available to Cloud Agents, then make the same servers available for teammates to install and configure in the Agent Window, IDE, and CLI.
Adding a Team MCP server to the Default marketplace does not install or enable it for every developer. Admins still control marketplace access and plugin installation modes. Each developer may also need to authenticate with the MCP provider.
Admins can link standalone Team MCP servers to the Default marketplace:
Cursor creates the Default marketplace if needed and links the existing MCP servers to it. The servers remain available to Cloud Agents while teammates gain the option to install and configure them locally.
Removing a linked MCP plugin from the marketplace or deleting the marketplace can delete the Team MCP server. This removes it for local users and Cloud Agents. Review the confirmation message before continuing.
Team marketplaces are available to everyone in their team by default. Under Marketplace Settings -> Marketplace Access, admins can restrict a marketplace to selected Organization Groups. Only members of the marketplace's team who belong to a selected group receive access. Team admins retain access.
Organization Groups can sync membership from your identity provider through SCIM. Manage membership in your identity provider, and Cursor syncs those updates to the Organization Group.
Existing marketplaces that use team-level SCIM directory groups keep that configuration. Cursor does not migrate those assignments automatically. Organizations without Organization Groups continue to use SCIM directory groups.
After setting marketplace access, choose how each plugin is distributed to that audience:
Use this flow to import a GitHub repository as a team marketplace:
Example repository to try:
When importing from GitHub, plugins are indexed when you first import the repository. You can refresh plugins in two ways:
For marketplaces created with "Import from Repo", Auto Refresh re-reads the full manifest on each push, so new plugins added to the repository are picked up automatically.
For marketplaces where plugins were added individually, Auto Refresh only updates existing plugins. Re-import the repository URL to pick up newly added plugins.
Developers can find team marketplaces in Customize.
Install Agent Plugins and Cursor Plugins from a marketplace. Cursor detects the format from the plugin manifest, so the installation flow is the same for both:
An Agent Plugin has a plugin.json manifest at its root. A Cursor Plugin has a
.cursor-plugin/plugin.json manifest. Team marketplaces can distribute either
format using the same access and installation modes described above.
You can also develop either format from ~/.cursor/plugins/local. See
Test plugins locally for the folder layout and when
Cursor loads it.
Share MCP server configurations using install links:
cursor://anysphere.cursor-deeplink/mcp/install?name=$NAME&config=$BASE64_ENCODED_CONFIGSee MCP install links for details on generating these links.
Open Customize in the sidebar to manage installed Agent Plugins, Cursor Plugins, MCP servers, rules, and skills from one page. Filter by user, workspace, or team scope to see what is installed.
Toggle personal and team-distributed MCP servers on or off from Customize:
Disabled servers won't load or appear in chat.
Manage rules and skills from Customize. Toggle individual rules between Always, Agent Decides, and Manual modes. Skills appear in the Agent Decides section and can be invoked manually with /skill-name in chat.
A workspaceOpen hook can return plugin paths to load on workspace open, which is useful when the set of plugins depends on the workspace itself.
Hooks reference
Register plugin paths from a workspaceOpen hook script
A plugin is a directory with a manifest and its components. Choose Agent Plugins when you want to package portable skills and MCP servers. Choose Cursor Plugins when you also need Cursor-specific components such as rules, agents, commands, hooks, or variables.
my-plugin/ plugin.json skills/ code-reviewer/ SKILL.md mcp.jsonAgent Plugins require a root plugin.json with the standard's schema identifier:
{ "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json", "name": "my-plugin", "description": "Portable code review tools", "version": "1.0.0", "author": { "name": "Your Name" }}Start from the Cursor Plugin template repository, or read the Agent Plugins authoring guide to create an Agent Plugin.
Before you publish, put either plugin format in ~/.cursor/plugins/local:
~/.cursor/plugins/local/my-pluginplugin.json
for an Agent Plugin or .cursor-plugin/plugin.json for a Cursor Plugin.After a reload, Cursor discovers plugins in this folder if local plugin imports are allowed.
On Teams and Enterprise, admins control this with Allow Local Plugin Imports under Dashboard -> Settings -> Security & Identity -> Marketplace and Plugins. The setting is off by default on Enterprise. If a marketplace plugin with the same name is already installed, that install takes precedence over the local copy.
For faster iteration, symlink your plugin repository:
ln -s /path/to/my-plugin ~/.cursor/plugins/local/my-pluginWhen your plugin is ready, submit it for review at cursor.com/marketplace/publish.
Cursor Plugins can use .cursor-plugin/marketplace.json for multi-plugin
repositories.
See the Plugins reference for the full manifest schema, component formats, and submission checklist.
Team and Enterprise marketplaces
Upgrade for private team marketplaces and organization-wide plugin distribution.
Yes. Every plugin is manually reviewed before it's listed. All plugins must be open source, and we review each update before publishing. See Marketplace security for details on vetting, update reviews, and how to report issues.
For a portable Agent Plugin, add a root plugin.json manifest and package
skills or MCP servers. For a Cursor Plugin, add a
.cursor-plugin/plugin.json manifest and any Cursor components you need.
See the Plugins reference for examples of both
formats.
Agent Plugins is an open, vendor-neutral specification for packaging skills and MCP servers into portable plugins. Cursor supports the standard, so spec-conformant plugins load in Cursor without changes. Cursor Plugins are developed in parallel and add Cursor-specific components like rules, agents, commands, hooks, and variables.
Search for a command to run...
Plugins package rules, skills, agents, commands, MCP servers, and hooks into distributable bundles.
Cursor supports the Agent Plugins open standard alongside its own plugin format. Install and manage them from the Customize page or browse official plugins in the Cursor Marketplace. For community plugins and MCP servers, browse cursor.directory. You can also build your own to share with other developers.
A plugin can bundle any combination of these components:
| Component | Available in | Description |
|---|---|---|
| Rules | Cursor Plugins | Persistent AI guidance and coding standards (.mdc files) |
| Skills | Both formats | Specialized agent capabilities for complex tasks |
| Agents | Cursor Plugins | Custom agent configurations and prompts |
| Commands | Cursor Plugins | Agent-executable command files |
| MCP Servers | Both formats | Model Context Protocol integrations |
| Hooks | Cursor Plugins | Automation scripts triggered by events |
Plugins bundle reusable components an agent can use. Agent Plugins is the open standard for packaging portable skills and MCP servers, much like Agent Skills defines a standard for individual skills. Cursor supports Agent Plugins alongside Cursor Plugins.
plugin.json manifest at the plugin root, packaging skills and MCP servers.cursor-plugin/plugin.json manifest, which add rules, agents, commands, hooks, and variablesA plugin that follows the Agent Plugins specification loads in Cursor without changes. Cursor Plugins continue to develop in parallel with the standard, so Cursor-specific components and marketplace features keep working as they do today.
Learn more at agent-plugins.org or read the specification on GitHub.
Plugins now ship with prebuilt canvases: shared setup templates your team can open and reuse.
Open a canvas from an installed plugin in Customize to get a guided starting point instead of configuring everything from scratch.
The Cursor Marketplace is where you discover and install official Cursor Plugins. Plugins are distributed as Git repositories and submitted through the Cursor team.
Every plugin is manually reviewed before it's listed. Browse official plugins at cursor.com/marketplace or search by keyword in Customize. For community plugins and MCP servers, browse cursor.directory.
Team marketplaces are available on Teams and Enterprise plans. They can distribute Agent Plugins and Cursor Plugins through the same marketplace.
Contact sales for unlimited team marketplaces and Enterprise admin controls.
Open Dashboard -> Plugins to manage Team Marketplaces.
On Enterprise plans, only admins can add team marketplaces from Dashboard -> Plugins.
The Default team marketplace connects shared plugins and MCP servers across Cursor. Admins can add Team MCP servers that are already available to Cloud Agents, then make the same servers available for teammates to install and configure in the Agent Window, IDE, and CLI.
Adding a Team MCP server to the Default marketplace does not install or enable it for every developer. Admins still control marketplace access and plugin installation modes. Each developer may also need to authenticate with the MCP provider.
Admins can link standalone Team MCP servers to the Default marketplace:
Cursor creates the Default marketplace if needed and links the existing MCP servers to it. The servers remain available to Cloud Agents while teammates gain the option to install and configure them locally.
Removing a linked MCP plugin from the marketplace or deleting the marketplace can delete the Team MCP server. This removes it for local users and Cloud Agents. Review the confirmation message before continuing.
Team marketplaces are available to everyone in their team by default. Under Marketplace Settings -> Marketplace Access, admins can restrict a marketplace to selected Organization Groups. Only members of the marketplace's team who belong to a selected group receive access. Team admins retain access.
Organization Groups can sync membership from your identity provider through SCIM. Manage membership in your identity provider, and Cursor syncs those updates to the Organization Group.
Existing marketplaces that use team-level SCIM directory groups keep that configuration. Cursor does not migrate those assignments automatically. Organizations without Organization Groups continue to use SCIM directory groups.
After setting marketplace access, choose how each plugin is distributed to that audience:
Use this flow to import a GitHub repository as a team marketplace:
Example repository to try:
When importing from GitHub, plugins are indexed when you first import the repository. You can refresh plugins in two ways:
For marketplaces created with "Import from Repo", Auto Refresh re-reads the full manifest on each push, so new plugins added to the repository are picked up automatically.
For marketplaces where plugins were added individually, Auto Refresh only updates existing plugins. Re-import the repository URL to pick up newly added plugins.
Developers can find team marketplaces in Customize.
Install Agent Plugins and Cursor Plugins from a marketplace. Cursor detects the format from the plugin manifest, so the installation flow is the same for both:
An Agent Plugin has a plugin.json manifest at its root. A Cursor Plugin has a
.cursor-plugin/plugin.json manifest. Team marketplaces can distribute either
format using the same access and installation modes described above.
You can also develop either format from ~/.cursor/plugins/local. See
Test plugins locally for the folder layout and when
Cursor loads it.
Share MCP server configurations using install links:
cursor://anysphere.cursor-deeplink/mcp/install?name=$NAME&config=$BASE64_ENCODED_CONFIGSee MCP install links for details on generating these links.
Open Customize in the sidebar to manage installed Agent Plugins, Cursor Plugins, MCP servers, rules, and skills from one page. Filter by user, workspace, or team scope to see what is installed.
Toggle personal and team-distributed MCP servers on or off from Customize:
Disabled servers won't load or appear in chat.
Manage rules and skills from Customize. Toggle individual rules between Always, Agent Decides, and Manual modes. Skills appear in the Agent Decides section and can be invoked manually with /skill-name in chat.
A workspaceOpen hook can return plugin paths to load on workspace open, which is useful when the set of plugins depends on the workspace itself.
Hooks reference
Register plugin paths from a workspaceOpen hook script
A plugin is a directory with a manifest and its components. Choose Agent Plugins when you want to package portable skills and MCP servers. Choose Cursor Plugins when you also need Cursor-specific components such as rules, agents, commands, hooks, or variables.
my-plugin/ plugin.json skills/ code-reviewer/ SKILL.md mcp.jsonAgent Plugins require a root plugin.json with the standard's schema identifier:
{ "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json", "name": "my-plugin", "description": "Portable code review tools", "version": "1.0.0", "author": { "name": "Your Name" }}Start from the Cursor Plugin template repository, or read the Agent Plugins authoring guide to create an Agent Plugin.
Before you publish, put either plugin format in ~/.cursor/plugins/local:
~/.cursor/plugins/local/my-pluginplugin.json
for an Agent Plugin or .cursor-plugin/plugin.json for a Cursor Plugin.After a reload, Cursor discovers plugins in this folder if local plugin imports are allowed.
On Teams and Enterprise, admins control this with Allow Local Plugin Imports under Dashboard -> Settings -> Security & Identity -> Marketplace and Plugins. The setting is off by default on Enterprise. If a marketplace plugin with the same name is already installed, that install takes precedence over the local copy.
For faster iteration, symlink your plugin repository:
ln -s /path/to/my-plugin ~/.cursor/plugins/local/my-pluginWhen your plugin is ready, submit it for review at cursor.com/marketplace/publish.
Cursor Plugins can use .cursor-plugin/marketplace.json for multi-plugin
repositories.
See the Plugins reference for the full manifest schema, component formats, and submission checklist.
Team and Enterprise marketplaces
Upgrade for private team marketplaces and organization-wide plugin distribution.
Yes. Every plugin is manually reviewed before it's listed. All plugins must be open source, and we review each update before publishing. See Marketplace security for details on vetting, update reviews, and how to report issues.
For a portable Agent Plugin, add a root plugin.json manifest and package
skills or MCP servers. For a Cursor Plugin, add a
.cursor-plugin/plugin.json manifest and any Cursor components you need.
See the Plugins reference for examples of both
formats.
Agent Plugins is an open, vendor-neutral specification for packaging skills and MCP servers into portable plugins. Cursor supports the standard, so spec-conformant plugins load in Cursor without changes. Cursor Plugins are developed in parallel and add Cursor-specific components like rules, agents, commands, hooks, and variables.
| Web Proxy Viewer | New URL | Original Page |