cursor/plugins
Cursor’s official plugin repository defines a manifest-based package format for bundling skills, rules, MCP servers and agent workflows. It offers concrete patterns for reusable coding-agent tooling.
Cursor’s repository is both a plugin specification and a marketplace of official integrations. A root **marketplace.json** indexes standalone directories, each carrying its own **plugin.json** manifest and optionally skills, rules and MCP configuration.
Use it as a reference when packaging repeatable agent behavior instead of copying prompts between repositories. The included patterns cover plugin scaffolding, agent-friendly CLIs, SDK integrations, memory updates, reviews and planner-worker-verifier handoffs.
Cursor’s repository is both a plugin specification and a marketplace of official integrations. A root **marketplace.json** indexes standalone directories, each carrying its own **plugin.json** manifest and optionally skills, rules and MCP configuration. Use it as a reference when packaging repeatable agent behavior instead of copying prompts between repositories. The included patterns cover plugin scaffolding, agent-friendly CLIs, SDK integrations, memory updates, reviews and planner-worker-verifier handoffs. The catalog mixes coding workflows with remote SaaS connectors, so installing a plugin can expand an agent’s data access and action surface. The supplied material describes structure and capabilities, but provides no compatibility, security or reliability results.
This gives Cursor users both a concrete plugin packaging reference and a distribution catalog for turning repeated prompts and workflows into versioned skills, rules, agents, and MCP integrations. Against broader portability efforts, it confirms a client-specific marketplace implementation, while its mixed local and remote integrations make manifest compliance only the start of adoption; permissions, trust, compatibility, and reliability still need separate review.