Cursor Plugins: Official Extension Marketplace
/plugins
Cursor Plugins deliver the official extension library for the Cursor AI editor, and the scope is genuinely wide — from code review canvases and team workflows to Gmail, Salesforce, and Gong integrations. Worth trying once you want Cursor to handle tasks beyond raw code generation, though the plugin system itself is still maturing, so expect occasional rough edges when authoring new plugins rather than just installing existing ones.
What Cursor Plugins are
Cursor Plugins are official extensions that extend the Cursor AI code editor's capabilities, covering developer workflows, productivity tools, and third-party service integrations. Each plugin is a standalone directory containing a manifest, TypeScript skills, agent rules, and optionally MCP server definitions — installed directly through Cursor's built-in marketplace.
Key features of the plugin system
- ✓Per-plugin manifest system with plugin.json defining name, author, category, and capabilities
- ✓TypeScript-based Cursor SDK for building apps, scripts, and automations that interact with the editor
- ✓Agent skills defined via SKILL.md files with frontmatter metadata
- ✓MCP server integration via mcp.json for connecting external tools and services
- ✓Rules system using .mdc files to guide agent behavior across different contexts
- ✓Marketplace manifest at the root exposing all plugins for discovery and installation
- ✓Create Plugin scaffold for bootstrapping new extensions with validation
- ✓Structured plugin directories with CHANGELOG.md and LICENSE files
What each plugin category does
- •Developer tooling: Team workflows (CI, code review, shipping automation), parallel task orchestration across cloud agents, and rigorous branch audits via plugins like Cursor Team Kit, Orchestrate, and Thermos
- •Productivity: Email management via Gmail, calendar scheduling, and file sharing through Google Drive and Calendar plugins
- •Third-party integrations: GitHub repo management, Salesforce CRM operations, Gong call insights, HubSpot contacts, Playwright browser testing, and numerous other SaaS connections
- •Agent memory: Continual Learning plugin maintains incremental transcript-driven memory updates for AGENTS.md using high-signal bullet points
- •Code review: PR Review Canvas renders diffs as navigable canvases grouped by importance; Agent Compatibility scans repos against reality
- •Documentation: Docs Canvas renders docs as navigable canvases for quick AI-assisted reference
Installing plugins from the marketplace
Open Cursor IDE and access the built-in marketplace to browse available plugins. Click Install on any plugin from the list — the marketplace.json at the repository root enumerates all available extensions. For manual installation, clone the repository and place a plugin directory at the appropriate location within your Cursor configuration, then restart the editor to load the new plugin.
Strengths
- ✓Official first-party plugins maintained by the Cursor team, ensuring consistent quality and compatibility
- ✓MIT licensing makes the entire collection free to use and modify
- ✓Wide range of third-party integrations covering major SaaS products developers actually use
- ✓TypeScript-based SDK makes plugin development familiar to most web and backend developers
- ✓Structured manifest format with skills, rules, and MCP definitions enables sophisticated agent behaviors
- ✓Create Plugin scaffold reduces friction for developers wanting to build their own extensions
Current limitations of the plugin system
- △The plugin system is young — authoring new plugins still has rough edges compared to mature extension ecosystems like VS Code
- △Plugin capabilities are bounded by Cursor's internal API surface, which limits what third-party developers can build
- △No self-hosted marketplace or private plugin registry documented, restricting use in air-gapped environments
- △Not all plugins have equal maturity — some integrations cover basic operations while others implement deep workflows
- △Community plugin ecosystem beyond this official repository is still emerging, limiting third-party options
- △Dependencies on MCP server availability for some integrations introduce reliability considerations outside Cursor's control
Alternatives and related tools
Frequently asked questions
Cursor Plugins offers over 30 official extensions spanning developer tools (code review, team workflows, agent orchestration), productivity (Gmail, Google Drive, Calendar), and integrations (GitHub, Salesforce, HubSpot, Playwright, Gong, and more). The full list is maintained in the marketplace.json at the repository root.
Open Cursor IDE and access its built-in marketplace to browse available plugins. Click Install on any plugin you want — no manual file placement required for standard marketplace installations. For manual installation, clone the repo and place a plugin directory in your Cursor config folder.
Yes — the Create Plugin scaffold in the repository lets you bootstrap new extensions with validation built in. Plugins are TypeScript-based, use a plugin.json manifest, and can include skills (SKILL.md), rules (.mdc files), and MCP server definitions (mcp.json) to define what the plugin does.
The Cursor SDK is a TypeScript library for building apps, scripts, and automations that interact with Cursor's internal capabilities. It provides the programmatic interface for reading files, running agent commands, and integrating with the editor's AI workflows from within a plugin.
Each plugin has a .cursor-plugin/plugin.json file defining its name, author, category, and description. A root-level marketplace.json aggregates all plugins for discovery. The manifest is where Cursor reads plugin metadata when installing or updating extensions.
Yes — the repository states MIT licensing for all plugins. This means you can use, modify, and distribute them freely, including for commercial purposes, as long as you retain the copyright notice.
The problem it solves
Cursor IDE's AI agent capabilities are effective in isolation, but without extensibility, every workflow beyond basic editing requires manual handoffs or external tooling. Developers working with third-party services, team-specific processes, or specialized code review pipelines had no native way to extend Cursor's behavior until a structured plugin system existed.
Who should try it — and who should skip
Try Cursor Plugins if you already use Cursor IDE and want to extend it with integrations your team relies on — GitHub management, Salesforce workflows, Gmail triage, or internal team processes. Skip this if you don't use Cursor, as the ecosystem is only useful inside that editor, or if you need a mature, battle-tested extension system with a large community ecosystem; VS Code Extensions are far more mature in that regard. Developers wanting to build custom tools inside Cursor will find the SDK and Create Plugin scaffold genuinely useful.
Is plugins worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of plugins.