Cursor plugin specification and official plugins
2.3k
Stars
172
Forks
19
Open issues
9
Contributors
AI Analysis
Cursor plugins is an official marketplace and specification for plugin development within the Cursor IDE, providing a curated collection of developer tool integrations, frameworks, and SaaS connectors. It serves IDE power users, AI-assisted developers, and teams adopting Cursor as their primary development environment—particularly those building workflows around AI agents. This repository is not for general developers; it's specifically for those using Cursor and wanting to extend its capabil...
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Official plugin ecosystem for Cursor IDE, enabling agent-augmented workflows for developer tools
Cursor plugins is the official marketplace and specification repository for extending Cursor IDE with pre-built workflows, agent skills, and integrations. Created by Cursor in January 2026, it provides scaffolding and reference implementations for agentic coding patterns (code review, documentation rendering, parallel task orchestration, CI automation). Built specifically for users of Cursor IDE who want composable, repeatable agent workflows. Real-world adoption is tied to Cursor IDE adoption and appears limited to early adopters; the repository is very new and adoption not independently verified outside Cursor's own ecosystem.
Repository created 2026-01-23, six months ago. Cursor IDE is an AI code editor founded 2022; this plugins repository represents formalization of its extensibility model. Mirrors OpenAI's plugins approach but tailored to agentic coding workflows rather than ChatGPT integrations. Positioned to grow as Cursor's multi-agent orchestration features mature.
89 stars in final 7 days; 2,172 total over 6 months represents rapid initial adoption relative to recency. Growth trajectory suggests early-stage hype and awareness-building. Repository itself is nascent, with 11 official plugins authored by Cursor or community contributors (Lauren Tan's pstack plugin). Growth likely driven by Cursor IDE's user base expansion and tooling announcements rather than organic discovery; baseline comparison suggests 32k-star parent repository (cursor/cursor) provides natural audience.
Adoption not verified beyond Cursor's internal use (Cursor-authored plugins include 'Cursor Team Kit' explicitly labeled for internal team workflows) and assumption of Cursor IDE user base. No case studies, public integrations, or third-party production deployments documented. Plugin submissions and external contributions (e.g., pstack by Lauren Tan) suggest early ecosystem participation, but scale and real-world adoption remain opaque.
Likely follows a declarative, manifest-driven plugin model: each plugin contains `.cursor-plugin/plugin.json` (metadata), `.cursor-plugin/marketplace.json` (registry), plus optional `skills/` (SKILL.md with frontmatter for agent capabilities), `rules/` (.mdc Cursor rules), and `mcp.json` (MCP server definitions). Appears designed for easy discovery and composition without tight coupling. README does not detail schema versioning, validation logic, or runtime loading mechanisms — these are inferred from structure only.
not documented in README
Last push 2026-06-29 (1 day before evaluation date), indicating active maintenance. Repository is 6 months old, so 'active' means consistent updates within a nascent codebase rather than sustained long-term effort. No evidence of stagnation; too early to assess long-term commitment.
ADOPT IF: you use Cursor IDE regularly, want repeatable multi-agent workflows for code review, docs, or CI automation, and accept early-stage tooling (6 months old, breaking changes possible). AVOID IF: you require stability guarantees, need cross-editor portability, or depend on mature plugin ecosystems with large third-party libraries. MONITOR IF: you are curious about Cursor's agentic coding model but not yet committed; watch for schema maturity, third-party adoption signals, and whether Cursor IDE gains enterprise adoption.
Independent dimensions
Mainstream potential
4/10
Technical importance
6/10
Adoption evidence
2/10
- Platform lock-in: plugins are Cursor IDE-specific and cannot transfer to VSCode, JetBrains, or other editors. Betting on Cursor IDE's long-term viability is necessary.
- Early specification instability: 6-month-old repository likely to experience breaking changes in manifest format, MCP integration, or skill APIs as Cursor refines its multi-agent model.
- Limited third-party ecosystem: 11 plugins (mostly Cursor-authored) is a thin marketplace. Few incentives for external developers to build if Cursor IDE adoption stalls.
- Adoption not independently verified: no public evidence of production deployments, no testimonials, no metrics. Growth may reflect awareness-building hype rather than actual use.
- Documentation and learning curve: README is sparse on runtime behavior, error handling, or troubleshooting. Likely requires hands-on Cursor IDE experience to navigate.
Cursor plugins will either mature into a self-sustaining marketplace ecosystem (if Cursor IDE adoption accelerates) or remain a niche tool for Cursor power users. Probability depends entirely on Cursor IDE's trajectory, not on the plugins repository's technical merit. Watch for: (1) enterprise adoption of Cursor IDE, (2) growth in third-party plugin submissions, (3) public case studies from teams using these plugins in production.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- TypeScript
- Last updated
- 1d ago
- Created
- 6mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
continual-learning: support user-owned cadence config and repo denylist
ForgeCat profiles for Cursor plugins
Docs: plugin install vs disable vs uninstall lifecycle and enabled-state ground truth
Add option to deactivate all cursor skills
how to remove depecated mcp server from cursor.directory
Open pull requests
Top contributors
Recent releases
No releases published yet.
Similar repos
cursor/cursor
Cursor is an AI-powered code editor that serves developers seeking IDE features...
PatrickJS/awesome-cursorrules
This is a curated collection of Cursor AI editor rules—configuration files in...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
cursor/plugins
this
|
2.3k | +44 | TypeScript | 7/10 | 1d ago |
|
cursor/cookbook
|
4k | — | TypeScript | 7/10 | 2d ago |
|
cursor/cursor
|
33k | — | — | 6/10 | 2mo ago |
 openai/plugins
|
4.2k | — | JavaScript | 7/10 | 10h ago |
|
PatrickJS/awesome-cursorrules
|
40.3k | — | JavaScript | 7/10 | 1mo ago |
 oslook/cursor-ai-downloads
|
3.2k | — | TypeScript | 7/10 | 2d ago |
OpenAI's ChatGPT plugin spec (archived); Cursor plugins adapted the pattern for agentic coding workflows rather than LLM chat integrations. Cursor plugins emphasize multi-agent orchestration, code review, and CI automation vs. OpenAI's service-integration focus.
Cursor cookbook is a growing collection of usage patterns and examples (3,955 stars). Plugins repository is more structured and registry-driven; cookbook is guides. Complementary roles.
VSCode has a mature extension marketplace with 60k+ published extensions and millions of installs. Cursor plugins is nascent; cannot predict reach or sustainability without longer history.
Cursor plugins encapsulate agent workflows; traditional task runners execute static scripts. Plugins are newer and more aligned with AI agent composition; adoption risk is higher due to platform lock-in (Cursor IDE dependency).