Plugins

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.

What plugins contain

A plugin can bundle any combination of these components:

The Agent Plugins standard

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.

• Agent Plugins: spec-conformant plugins with a plugin.json manifest at the plugin root, packaging skills and MCP servers
• Cursor Plugins: plugins with a .cursor-plugin/plugin.json manifest, which add rules, agents, commands, hooks, and variables

A 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.

Cursor Plugin canvases

Plugins now ship with prebuilt canvases: shared setup templates your team can open and reuse.

• Hex Canvas — Build data visualizations. At Cursor, we use the Hex Canvas to explore and share analytics.
• Atlassian Canvas — See a realtime view of your issues, projects, and documents from Jira and Confluence.

Open a canvas from an installed plugin in Customize to get a guided starting point instead of configuring everything from scratch.

The marketplace

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

Team marketplaces are available on Teams and Enterprise plans. They can distribute Agent Plugins and Cursor Plugins through the same marketplace.

• Teams plan: up to 1 team marketplace
• Enterprise plan: unlimited team marketplaces

Contact sales for unlimited team marketplaces and Enterprise admin controls.

Open Dashboard -> Plugins to manage Team Marketplaces.

Default team marketplace

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.

Migrate existing Team MCPs

Admins can link standalone Team MCP servers to the Default marketplace:

1. Open Dashboard -> Integrations & MCP.
2. Find Team MCP Servers.
3. Select Add to Team Marketplace in the migration prompt.
4. Open Dashboard -> Plugins to review the Default marketplace, its access, and plugin installation modes.

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.

Marketplace access

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.

How does SCIM work?

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.

Plugin installation modes

After setting marketplace access, choose how each plugin is distributed to that audience:

• Default Off: Developers can find the plugin and choose whether to install it.
• Default On: The plugin is installed by default, but developers can opt out.
• Required: The plugin is always installed and cannot be uninstalled.

Add a team marketplace

Use this flow to import a GitHub repository as a team marketplace:

1. Go to Dashboard -> Plugins.
2. In Team Marketplaces, click Add Marketplace.
3. Follow the instructions to create a marketplace from scratch, or use "Import from Repo" if importing from GitHub.
4. Add and review plugins using "Add to Marketplace".
5. Under Marketplace Settings, set Marketplace Access, optionally enable Auto Refresh, then save.

Example repository to try:

• fieldsphere/cursor-team-marketplace-template

Keep plugins up to date

When importing from GitHub, plugins are indexed when you first import the repository. You can refresh plugins in two ways:

• Automatically: Turn on Enable Auto Refresh to update plugins automatically whenever changes are pushed to the branch the marketplace tracks. This requires the Cursor GitHub App installed on the repository. Cursor re-indexes a marketplace at most once every 10 minutes, batching rapid pushes to the latest commit.
• Manually: Click "Refresh" to manually update.

Where developers find team marketplaces

Developers can find team marketplaces in Customize.

• Open Customize in the sidebar
• Look for plugins from your team marketplace.
• Install Default Off plugins directly from that panel.
• Default On plugins are installed automatically, but developers can opt out.
• Required plugins are installed automatically and cannot be uninstalled.
• Install and configure marketplace MCP servers for use in the Agent Window, IDE, and CLI.

Installing plugins

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:

1. Open Customize in the sidebar.
2. Find the plugin you want to use.
3. Select Install and choose a project or user scope.

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 load either format directly from ~/.cursor/plugins/local while developing a plugin. See Test plugins locally.

MCP Apps deeplinks

Share MCP server configurations using install links:

cursor://anysphere.cursor-deeplink/mcp/install?name=$NAME&config=$BASE64_ENCODED_CONFIG

See MCP install links for details on generating these links.

Managing installed plugins

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.

MCP servers

Toggle personal and team-distributed MCP servers on or off from Customize:

1. Open Customize in the sidebar
2. Find the MCP server you want to change
3. Use the toggle to enable or disable it

Disabled servers won't load or appear in chat.

Rules and skills

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.

Using the workspaceOpen hook

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.

Creating plugins

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.json

{  "$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.

Test plugins locally

Before you publish, load either plugin format from ~/.cursor/plugins/local:

1. Create a folder for your plugin: ~/.cursor/plugins/local/my-plugin
2. Copy your plugin files into that folder. Include either a root plugin.json for an Agent Plugin or .cursor-plugin/plugin.json for a Cursor Plugin.
3. Restart Cursor, or run Developer: Reload Window.
4. Verify your plugin components load in Cursor, such as rules, skills, or MCP servers.

For faster iteration, symlink your plugin repository:

ln -s /path/to/my-plugin ~/.cursor/plugins/local/my-plugin

When 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.

FAQ