Cursor plugins are installable bundles that add rules, skills, subagents, slash commands, hooks and MCP servers to Cursor in one step. To install one, open Customize in the sidebar, find the plugin, click Install and pick project or user scope; many official plugins also install from Agent chat with /add-plugin <name>. Use a plugin when you want to ship several of those pieces together. If all you need is one tool connection, a plain MCP server is enough.
Interest is climbing because the official repository, cursor/plugins, is on GitHub's daily trending page on November 20, 2026, with about 17,700 stars. Its marketplace file lists 156 plugins that day, and new ones land almost daily: Expensify, Strava, FactSet, SAP S/4HANA Cloud and a renamed Intuit QuickBooks plugin all merged between November 16 and 19. This guide covers what a plugin contains, how installing and team distribution work, how to build and validate one, and the security model, based on Cursor's plugin docs, the plugin reference and our own test of the validator.
What is inside a Cursor plugin
A plugin is a folder with a manifest and any mix of six component types. Cursor's docs list them like this:
| Component | What it does | Default location |
|---|---|---|
| Rules | Persistent guidance and coding standards | rules/*.mdc |
| Skills | Task instructions the agent loads when relevant | skills/<name>/SKILL.md |
| Agents | Subagent definitions with their own prompt | agents/*.md |
| Commands | Actions you trigger by name | commands/*.md |
| Hooks | Scripts that run on agent, Tab or workspace events | hooks/hooks.json |
| MCP servers | Tool connections to outside services | mcp.json |
If the manifest names a path for a component (for example "skills": "./my-skills/"), that path replaces the default folder; Cursor does not scan both. A plugin with only a SKILL.md at its root, and no skills/ folder, is treated as a single skill plugin.
Real plugins show the range. The official GitHub plugin is almost nothing but an mcp.json pointing at GitHub's hosted MCP server, plus a declared GITHUB_PERSONAL_ACCESS_TOKEN variable. Ralph Loop, by contrast, ships three skills and two hooks (afterAgentResponse and stop) that feed the same prompt back after every turn. Continual Learning pairs a subagent with a stop hook that updates your AGENTS.md file from session transcripts.
Two formats: Cursor Plugins and Agent Plugins
Cursor now loads two manifest formats:
- Cursor Plugins keep the manifest at
.cursor-plugin/plugin.jsonand can use every component above, plus variables. - Agent Plugins put
plugin.jsonat the plugin root and follow the vendor neutral Agent Plugins 1.0.0 specification. That format only covers skills and MCP servers, so it is the one to pick when the same bundle should work in other agents. The spec's steering committee includes maintainers from Amazon, Cursor, Microsoft, OpenAI and Vercel.
One porting trap: Cursor expands ${CURSOR_PLUGIN_ROOT} (and ${CLAUDE_PLUGIN_ROOT}) to the install path inside mcp.json, but it does not expand the standard's ${PLUGIN_ROOT} and ${PLUGIN_DATA}. A portable plugin that relies on those two will start its MCP server from the wrong folder in Cursor.
The skills inside both formats are ordinary agent skills, the same SKILL.md folders that Claude Code, Codex and Copilot read. That is why one skill can ship as a Cursor plugin, a Claude Code plugin and a loose folder at once. Our Superpowers guide shows one large skills plugin installed across more than a dozen agents.
How to install Cursor plugins
From the app, the flow is the same for both formats:
- Open Customize in the sidebar.
- Search for the plugin or browse the Cursor Marketplace.
- Click Install and choose a project or user scope.
- If the plugin declares variables (an API token, a database URL), set them in the dashboard under Plugins, then Configure.
Many READMEs in the official repo also give a one line install from Agent chat, such as /add-plugin advisor. After installing, the same Customize page lets you switch individual rules between Always, Agent Decides and Manual, toggle MCP servers on or off, and call skills by name with /skill-name.
Community plugins and MCP servers that are not in the official marketplace are listed on cursor.directory. Those are not covered by Cursor's review, so read them before installing.
Team marketplaces
On Teams and Enterprise plans an admin can run a private marketplace from Dashboard, Plugins & MCPs. Teams get one team marketplace plus the built in Default marketplace; Enterprise has no limit. A marketplace can be imported from GitHub, GitLab, Bitbucket or Azure DevOps, and each plugin gets an install mode: Default Off (members opt in), Default On (installed, members can remove it) or Required (always installed). With Auto Refresh on a GitHub import, Cursor reindexes at most once every 10 minutes after a push. Members can also publish a personal skill from ~/.cursor/skills/ to the Default marketplace, which wraps that one skill in its own plugin.
Cursor plugin vs MCP server
This is the most common question, and the answer is that one can contain the other. An MCP server is a single program that gives the agent tools, resources and prompts. A plugin is a package that can include one or more MCP server configs next to rules, skills, commands and hooks.
| Question | Plain MCP server | Cursor plugin |
|---|---|---|
| What it adds | Tools from one service | Any mix of rules, skills, agents, commands, hooks, MCP |
| Where it is configured | .cursor/mcp.json or ~/.cursor/mcp.json | Plugin manifest, installed from Customize |
| Works in other agents | Yes, any MCP client | Agent Plugins format yes; Cursor Plugins format is Cursor specific |
| Team rollout | Team MCP servers | Marketplace with Default Off, Default On or Required |
| Secrets | Env vars or headers you manage | Declared variables, values set in the dashboard |
Pick a bare MCP server when you only need the tools, or when the same server must also run in Claude Code, Codex or VS Code; our guide to running an MCP server locally shows the config for each. Pick a plugin when the tools need instructions to be used well (a skill that explains your deploy process, a rule that bans a risky command) or when you want a team to get the whole setup in one click.
Token cost follows from the same split. Skills only put their name and description in context until they are used, while every enabled MCP server sends its full tool list. If a plugin bundles a large MCP server you rarely use, switching that server off in Customize trims context without removing the plugin's skills and rules.
How to create a Cursor plugin
The minimum Cursor Plugin is a folder with .cursor-plugin/plugin.json containing a name. Everything else is optional. A practical layout:
team-guard/
.cursor-plugin/plugin.json
rules/pnpm.mdc
skills/release-notes/SKILL.md
commands/lint.md
hooks/hooks.json
mcp.json
{
"name": "team-guard",
"displayName": "Team Guard",
"version": "0.1.0",
"description": "House rules, a release notes skill and one MCP server.",
"author": { "name": "Your Team" },
"license": "MIT"
}
The rules for names and paths are strict. The name may use only lowercase letters, digits, hyphens and periods, and must start and end with a letter or digit. All paths must be relative, with no .. and no absolute paths. Rules, skills, agents and commands each need YAML frontmatter with a description. Hooks use the events documented in Cursor's hooks reference, such as beforeShellExecution, afterFileEdit and stop.
To test it, copy the folder to ~/.cursor/plugins/local/team-guard, run Developer: Reload Window and check Customize for the components. Two catches from the docs: a symlink there only loads if its target is inside that same folder, and on Enterprise the Allow Local Plugin Imports setting is off by default. If a marketplace plugin with the same name is installed, it wins over your local copy. The official Create Plugin plugin can scaffold this structure for you.
To publish, push the plugin to a public Git repository and submit the link at cursor.com/marketplace/publish. A repository with several plugins needs .cursor-plugin/marketplace.json at its root.
What we found validating plugins
We ran the official repo's own validator, which checks marketplace.json and every plugin.json against Cursor's published JSON schemas. All 156 plugins passed. Our test plugin with both manifests also passed, and its root plugin.json validated against the Agent Plugins 1.0.0 schema.
Then we broke it on purpose:
- An uppercase name with an underscore (
Team_Guard) failed the name pattern, and the validator also flagged that it no longer matched the marketplace entry. - An extra manifest field (
permissions) failed, because the Cursor schema allows no unknown top level keys. - Version 0.1.0 in
.cursor-plugin/plugin.jsonand 0.2.0 in the rootplugin.jsonfailed with "manifest versions differ". Keep versions in sync if you ship both formats. - A double hyphen (
team--guard) passed Cursor's schema but failed the Agent Plugins schema, which bans--and..in names. Avoid both if you want one name everywhere.
None of these checks open your skills or hooks, so frontmatter mistakes and broken scripts only show up when you load the plugin in Cursor.
Are Cursor plugins safe?
Cursor's marketplace security page says every official plugin is reviewed by hand before listing, all marketplace plugins must be open source, updates are reviewed rather than pulled automatically, and plugins respect your MCP allowlist and blocklist. Problem plugins can be reported to security-reports@cursor.com.
That still leaves real risk on your side. Hooks are shell commands that run on your machine at events like stop or beforeShellExecution, and a bundled MCP server can reach whatever its token allows. Read hooks/hooks.json and any scripts before you install, give tokens the narrowest scope that works, and treat cursor.directory listings as unreviewed. Our note on the tampered Claude Code extension is a reminder that marketplaces can be abused.
FAQ
Are Cursor plugins free?
Cursor's docs list no separate price for installing marketplace plugins. The services a plugin connects to may cost money (a SaaS account, API usage), and private team marketplaces need a Teams or Enterprise plan.
Where are Cursor plugins on GitHub?
The official plugins and the manifest schemas live at github.com/cursor/plugins. Each plugin is a folder there with its own .cursor-plugin/plugin.json, and the repo includes the validate-plugins.mjs script we used.
Can I use Claude Code plugins in Cursor?
Often with little change. Skills and MCP configs are shared formats, and Cursor expands ${CLAUDE_PLUGIN_ROOT} in mcp.json. A Claude Code plugin still needs a Cursor manifest (.cursor-plugin/plugin.json) or an Agent Plugins plugin.json, and hooks should be checked against Cursor's event names. See our Claude Code vs Cursor comparison for how the two tools differ overall.
Do Cursor plugins work in the Cursor CLI?
Cursor's docs say team marketplace MCP servers can be installed and configured for the Agent Window, the IDE and the CLI. Rules, skills and hooks depend on each surface, so check the plugin's README for what it supports.
How do I remove a Cursor plugin?
Open Customize, filter by user, workspace or team scope, and uninstall it there. Plugins your admin marked Required cannot be removed by members.



