Official plugin spec and marketplace repo for Cursor: bundles rules, skills, MCP servers, agents, and hooks for AI-powered dev workflows.
What it does
Cursor Plugins is the official multi-plugin marketplace repository for Cursor, the AI code editor. Each plugin bundles rules, skills, agents, MCP servers, commands, and hooks into a distributable Git-based package. The repo ships 11 official plugins spanning memory, orchestration, code review, docs,
Cursor Plugins turn the Cursor editor into a composable platform, not just an AI chat window. Instead of wiring up rules, MCP servers, and agent prompts by hand on every machine, a plugin bundles all of that into a single Git repo that installs in one step.
The official repo at cursor/plugins is both the specification and the reference implementation. It defines the .cursor-plugin/plugin.json manifest format and ships 11 plugins built by the Cursor team, covering everything from incremental memory updates (Continual Learning) to parallel cloud-agent orchestration (Orchestrate) to interactive PR diffs rendered as navigable Canvases (PR Review Canvas). Per the README, plugins are standalone directories at the repo root, each with its own manifest, a skills/ folder, a rules/ folder, an mcp.json, and standard changelog and license files.
A plugin can include any combination of six component types: Rules (.mdc files for persistent AI guidance), Skills (specialized agent capabilities), Agents (custom prompts and configs), Commands (agent-executable scripts), MCP Servers (Model Context Protocol integrations), and Hooks (event-triggered automation). The root .cursor-plugin/marketplace.json lists all plugins; each plugin carries its own plugin.json manifest. Install from Cursor's Customize page, or browse the Cursor Marketplace at cursor.com/marketplace. Community plugins live separately at cursor.directory.
The 11 official plugins each solve a distinct workflow gap:
AGENTS.md using high-signal bullets only.@cursor/sdk, covering runtime selection, auth, streaming, MCP, and error handling.The non-obvious gotcha: hooks execute as event-triggered scripts, so ordering and side-effects matter when multiple plugins attach hooks to the same event. There is no documented hook-priority system in the spec, which means plugin conflicts in hook-heavy setups require manual auditing. If you are choosing between a private Git repo team marketplace and a cursor.directory community plugin, the private repo path gives you required/optional distribution and SCIM group sync, but it needs a Cursor Teams or Enterprise plan; cursor.directory is open to anyone but carries no managed rollout controls.
Cursor Plugins flip team AI tooling from a suggestion into infrastructure. The team marketplace model, with required plugins pushed via SCIM-synced groups, means a platform engineer can standardize agent memory, review workflows, and MCP integrations across an entire org from a single Git repo. That is closer to an internal developer platform than a plugin store.
Features
Field notes
Reviewed Jun 26, 2026
Best for
Builder outcomes
Watch out
Tested with
Cost
Private team marketplace features including required/optional plugin distribution and SCIM group sync require a Cursor Teams or Enterprise plan. The cursor.directory community path and public marketplace are open to anyone.
Cursor Plugins is the official plugin specification and marketplace repository for Cursor, the AI code editor. It defines a standard manifest format (`.cursor-plugin/plugin.json`) for distributable bundles that can include rules, skills, agents, MCP servers, commands, and hooks. The repository ships 11 plugins built by the Cursor team, covering workflows like parallel agent orchestration, incremental memory, PR review, and SDK integration. Per the README, the repo is MIT-licensed and serves as both the spec reference and the source for official marketplace plugins.
Install by opening Cursor's Customize page and browsing or searching the Cursor Marketplace at cursor.com/marketplace; each plugin installs from its Git repository in one step. To build your own, use the `create-plugin` plugin included in the repo, which scaffolds and validates the plugin directory structure, including the `.cursor-plugin/plugin.json` manifest, `skills/`, `rules/`, and `mcp.json` files. To publish to the official marketplace, submit through the Cursor team via cursor.com/marketplace (the Publish link); every official listing is manually reviewed before it appears. Community plugins can be shared without review via cursor.directory.
Yes, the repository and all official plugins it contains are released under the MIT license. Any developer can clone the repo, use the plugins locally, or build new plugins without a paid plan. Team marketplace features, specifically required/optional plugin distribution to groups and SCIM identity-provider sync, require a Cursor Teams or Enterprise plan; the docs note that Teams supports one team marketplace and Enterprise supports unlimited, with sales contact required for Enterprise admin controls.
Cursor Plugins is best for teams that want to standardize AI tooling across many developers from a single Git repository. The team marketplace model lets a platform engineer push required plugins to distribution groups synced via SCIM, so every developer gets the same rules, agent memory setup, and MCP integrations automatically. Individual developers benefit most from the parallel orchestration plugins (Orchestrate, Thermos) for large tasks and code audits, and from Continual Learning for keeping an `AGENTS.md` memory file current without manual effort.
The official Cursor Marketplace (cursor.com/marketplace) lists plugins that have been manually reviewed by the Cursor team before publication, per the docs. It is the source for first-party and vetted third-party plugins and supports team marketplace distribution with required/optional assignment and SCIM sync. The cursor.directory is a separate community resource for plugins and MCP servers that anyone can list without a formal review process; it offers broader coverage but no managed rollout controls. If standardized, enforced distribution across a team matters, the official marketplace and its Git-based team marketplace path is the right choice.
The plugin spec does not document a hook-execution priority system, so if multiple installed plugins attach hooks to the same editor or repo event, conflicts and unexpected side-effects require manual auditing. Plugins can include MCP servers and event-triggered scripts, so reviewing each plugin's `mcp.json` and hooks before installation is important to understand what external services it contacts. Team marketplace distribution and SCIM group sync are gated behind paid Cursor plans. Finally, official marketplace submission goes through a manual review process, which introduces a publication lag for teams building proprietary plugins they want listed publicly.