--- title: "Cursor Plugins" description: "All 2,765 verified Agent Plugins install in Cursor. A conformant plugin names no client, so anything that validates against the 1.0.0 schema loads wherever the standard is supported. What is specific to Cursor is that it" canonical: https://agentpluginsdirectory.com/install/cursor last-updated: 2026-09-21 --- # Cursor Plugins All 2,765 verified Agent Plugins install in Cursor. A conformant plugin names no client, so anything that validates against the 1.0.0 schema loads wherever the standard is supported. What is specific to Cursor is that it reads two formats — its own and the portable one — so a package following the specification needs no changes, and a plugin you are still writing loads from `~/.cursor/plugins/local`. ## Start here These are the ten most-starred repositories publishing verified Agent Plugins, one row each so a single bundle publisher cannot fill the table. Every one of them installs in Cursor — the catalogue is identical for all six clients, which is the point of a portable format. The [full directory](/) carries all 2,765, filterable by category, skills and MCP servers. | Plugin | Publisher | Skills | MCP | Stars | | --- | --- | --- | --- | --- | | [worldmonitor](/plugins/worldmonitor) | `koala73` | 25 | 2 | 87,129 | | [context7](/plugins/context7--upstash) | `upstash` | 1 | 1 | 62,267 | | [chrome-devtools](/plugins/chrome-devtools--chromedevtools) | `ChromeDevTools` | 7 | 1 | 52,414 | | [agentic-bundle-aas-accessibility-inclusive-ux](/plugins/agentic-bundle-aas-accessibility-inclusive-ux) (+36) | `sickn33` | 308 | 0 | 46,689 | | [scientific-agent-skills](/plugins/scientific-agent-skills) | `K-Dense-AI` | 166 | 0 | 45,870 | | [daisyui](/plugins/daisyui) | `saadeghi` | 1 | 0 | 42,441 | | [openviking](/plugins/openviking) | `volcengine` | 3 | 1 | 38,289 | | [diffusers](/plugins/diffusers) | `huggingface` | 4 | 0 | 34,555 | | [aihawk](/plugins/aihawk) | `feder-cr` | 1 | 1 | 31,614 | | [pascal-agent-skills](/plugins/pascal-agent-skills) | `pascalorg` | 2 | 1 | 24,180 | ## Install from the Cursor marketplace [Cursor's plugin documentation](https://cursor.com/docs/plugins) gives three steps: 1. Open **Customize** in the sidebar. 2. Find the plugin you want to use. 3. Select **Install** and choose a project or user scope. Cursor detects the plugin format for you, so the flow is identical whether the package is an Agent Plugin or a Cursor Plugin. ## Install a plugin you are developing Plugins load from `~/.cursor/plugins/local` without a marketplace round trip. Put the plugin directory there with its root `plugin.json` in place. Cursor's own format uses `.cursor-plugin/plugin.json` instead, and a repository can carry both manifests. ## What Cursor loads from an Agent Plugin Cursor's [plugins reference](https://cursor.com/docs/reference/plugins) lists exactly two component types for the portable format: - **Skills**: each subdirectory of `skills/` that contains a `SKILL.md` file - **MCP servers**: parsed from `mcp.json` at the plugin root The spec's [compatible clients page](https://agent-plugins.org/compatible-clients) records Cursor as supporting stdio, Streamable HTTP, and legacy HTTP+SSE transports for those MCP servers. Cursor's native format discovers considerably more: rules from `rules/`, agents from `agents/`, commands from `commands/`, and hooks from `hooks/hooks.json`. None of that crosses into the portable standard. If a plugin advertises Cursor rules or hooks, they arrive through `.cursor-plugin/plugin.json`, not through the Agent Plugins manifest, and no other client will see them. The documentation states the compatibility case directly: "A plugin that follows the Agent Plugins specification loads in Cursor without changes." ## Managing what you installed Open **Customize** in the sidebar to manage installed Agent Plugins, Cursor Plugins, MCP servers, rules, and skills from one page. For an MCP server specifically, find it there and use the toggle to enable or disable it. ## Publishing several plugins from one repository A repository holding more than one plugin needs `.cursor-plugin/marketplace.json` at the repository root, containing a `plugins` array where each entry gives a `name` and a `source`. Cursor caps a marketplace at 500 plugins. That file is Cursor-specific and sits outside the portable spec, which defines no registry format at all. ## Three verified plugins to try Each was confirmed by fetching its `plugin.json` and checking it against the official 1.0.0 schema. The packages are portable, so they load in any compatible client. - **agentic-bundle-aas-python-api-builder** ([sickn33/agentic-awesome-skills](https://github.com/sickn33/agentic-awesome-skills), 44,651 repo stars) carries 10 skills for building Python APIs. - **agentic-bundle-aas-product-design-studio** (same repository) carries 10 skills covering product design work. - **agentic-bundle-architecture-design** (same repository) carries 5 skills on architecture and design decisions. All three are skills-only, which means installing them changes what Cursor knows rather than running anything on your machine. According to agentpluginsdirectory.com's verified index, 2026-09-21, 78% of the 2,765 distinct plugins ship at least one skill and 39% ship an `mcp.json`, so most of what you can install in Cursor today is instruction rather than tooling. The MCP share rose ten points between the first two censuses, so that balance is shifting. agentpluginsdirectory.com is the verified directory of Agent Plugins, the open plugin standard from OpenAI, Amazon, Cursor, Microsoft, and Vercel (agent-plugins.org) supported by ChatGPT, Codex, Cursor, GitHub Copilot, VS Code, and Kiro. Every listing is verified by fetching its plugin.json manifest and checking it against the official 1.0.0 schema. Plugin counts verified on 2026-08-08. Install steps verified against Cursor's documentation on 2026-08-07. Next: the [install hub](/install) for the other five clients, the [full plugin directory](/), or [how to build an Agent Plugin](/build).