What is Cursor Plugins? A catalogue for agent extensions
What is Cursor Plugins? A catalogue for agent extensions
Read the marketplace as a collection of independently packaged plugins, not one installed runtime
What you will learn
- Start with the two manifests
- Identify what the client loads
- Keep the review bounded
Before you start
- A disposable client profile
- One selected plugin
- The pinned repository revision
Turn a promising catalogue entry into a repeatable team decision
Key takeaways
- The root file indexes plugins.
- Each plugin has its own manifest and component mix.
- Capabilities are selected one entry at a time.
Start with the two manifests
At the pinned revision, the root `.cursor-plugin/marketplace.json` indexes plugin entries and their source directories. A selected directory has its own `.cursor-plugin/plugin.json` describing that plugin. Installing one entry does not mean every directory in the repository runs.
The catalogue mixes agent workflow packages, rules, skills and external integrations. The `create-plugin` entry provides authoring assistance, while the GitHub entry declares a remote MCP connection. Their operational and credential needs are different.
Identify what the client loads
The plugin schema permits paths to skills, rules, agents, commands and hooks, plus MCP server configuration and user variables. A manifest describes these surfaces; the client decides how to load and execute them.
A README table is useful for discovery, but its descriptions are not evidence that every integration has been installed or authenticated. Check the chosen directory, manifest and files before drawing a capability claim.
Keep the review bounded
This series inspects official repository files at commit `d0ef80d`. It does not install Cursor, execute a hook, authenticate GitHub MCP or compare agent results.
The nine chapters follow one reader from selection to installation planning, architecture, source validation, cost, security, alternatives and a controlled pilot. Each choice depends on the plugin actually selected.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Choose one plugin and read its manifest.
- 2
List its declared skills, hooks, MCP servers and variables.
- 3
Separate catalogue claims from a client-side test.
Copy-ready example
marketplace entry -> source directory -> plugin.json
plugin.json -> skills | rules | hooks | MCPFrequently asked questions
Is this a single AI agent?
No. It is a repository of independently packaged extensions for agent clients.
Did this review run a plugin?
No. It is a fixed-source editorial analysis.
Sources
- Cursor Plugins / README.mdSource checked 2026-10-08
- Cursor Plugins / .cursor-plugin/marketplace.jsonSource checked 2026-10-08
- Cursor Plugins / schemas/plugin.schema.jsonSource checked 2026-10-08
- Cursor Plugins / create-plugin/.cursor-plugin/plugin.jsonSource checked 2026-10-08
- Cursor Plugins / third_party/github/.cursor-plugin/plugin.jsonSource checked 2026-10-08