Claude Code vs Codex vs Cursor plugins

Updated November 4, 2026

In the HOL catalog, 710 plugins declare Claude Code, 552 declare Codex and 216 declare Cursor. 367 declare both Claude Code and Codex. The three directories ask for different things: Codex turns away plugins with lifecycle hooks or more than one MCP server, Cursor lists only open-source plugins, and Claude blocks unpinned npx and uvx launchers.

At a glance

Catalog size, overlap and directory rule counts for Claude Code, Codex and Cursor plugins.
	Claude Code	Codex	Cursor
Plugins in the HOL catalog	710	552	216
Also declare Claude Code	–	367 (66.5%)	184 (85.2%)
Also declare Codex	367 (51.7%)	–	124 (57.4%)
Also declare Cursor	184 (25.9%)	124 (22.5%)	–
Public directory	Claude plugin directory	ChatGPT and Codex plugin directory	Cursor Marketplace
Rules that block	14	7	6
Rules that hold for review	7	1	0
Rules that warn	2	0	1

How many plugins work in two of them

Each runtime reads its own manifest, so one repository can ship to all three. The pair bars count plugins whose listing declares both runtimes; a plugin that declares all three counts in every pair.

Plugins in the HOL catalog that declare each runtime, then each pair of runtimes. Catalog read November 3, 2026.

What each directory requires

The rules come from each directory's own submission pages, read on October 30, 2026. “No rule in the checklist HOL reads” means the page sets no rule for that topic, not that anything goes.

Plugin directory requirements by topic for the Claude plugin directory, the ChatGPT and Codex plugin directory and the Cursor Marketplace.
Topic	Claude plugin directory	ChatGPT and Codex plugin directory	Cursor Marketplace
Manifest	BlocksNo .claude-plugin/plugin.json in the plugin folderPlugin pre-submission checklist Blocksplugin.json is not valid JSONPlugin pre-submission checklist	BlocksNo plugin.json or .codex-plugin/plugin.jsonBuild plugins Blocksplugin.json is not valid JSONBuild plugins	BlocksNo .cursor-plugin/plugin.json or plugin.jsonPlugins reference: submission checklist Blocksplugin.json is not valid JSONPlugins reference: submission checklist BlocksManifest paths are absolute or leave the plugin folderPlugins reference: submission checklist
Plugin name	BlocksPlugin name has non-ASCII charactersPlugin pre-submission checklist WarningPlugin name is not lowercase kebab-case (up to 64 characters)Plugin pre-submission checklist BlocksPlugin name is a reserved wordPlugin pre-submission checklist Held for reviewPlugin name is made only of generic wordsPlugin pre-submission checklist	BlocksPlugin name is missing, over 64 characters or not kebab-caseSubmit a plugin	BlocksPlugin name is missing or not lowercase kebab-casePlugins reference: submission checklist
Description, author and version	Warningdescription, author or version is missing from plugin.jsonPlugin pre-submission checklist	Blocksversion, description or author.name is missingSubmit a plugin	WarningNo descriptionPlugins reference: submission checklist
README	BlocksREADME missing or under 40 wordsPlugin pre-submission checklist	No rule in the checklist HOL reads	BlocksNo README.mdPlugins reference: submission checklist
License	BlocksNo licensePlugin pre-submission checklist	No rule in the checklist HOL reads	BlocksNo open-source licensePlugins
Logo	No rule in the checklist HOL reads	Held for reviewNo logo in the manifestSubmit a plugin	No rule in the checklist HOL reads
Lifecycle hooks	Blockshooks/hooks.json is invalidPlugin pre-submission checklist	BlocksPlugin contains lifecycle hooksBuild plugins	No rule in the checklist HOL reads
MCP servers	Blocks.mcp.json cannot be parsedPlugin pre-submission checklist BlocksA remote MCP server URL is not https or wssPlugin pre-submission checklist Held for reviewAn MCP server ships as a .mcpb or .dxt bundlePlugin pre-submission checklist	BlocksA remote MCP server is not a public https endpointSubmit a plugin BlocksMore than one MCP serverSubmit a plugin	No rule in the checklist HOL reads
Package launchers (npx, uvx)	Blocksnpx, uvx or another launcher runs an unpinned packagePlugin pre-submission checklist Held for reviewA launcher runs a package from a registryPlugin pre-submission checklist BlocksPackage-manager config sets a custom registry next to a launcherPlugin pre-submission checklist Held for reviewpackage.json with a lockfile at the plugin rootPlugin pre-submission checklist	No rule in the checklist HOL reads	No rule in the checklist HOL reads
Files and size	BlocksmacOS or Windows system files in the plugin folderPlugin pre-submission checklist BlocksSymbolic links or Git submodules in the plugin folderPlugin pre-submission checklist BlocksRepository too large to validatePlugin pre-submission checklist Held for reviewFiles over 256 KiB that are not images or fontsPlugin pre-submission checklist Held for reviewMore than 512 files in the pluginPlugin pre-submission checklist Held for reviewBinary files the validator cannot inspectPlugin pre-submission checklist	No rule in the checklist HOL reads	No rule in the checklist HOL reads

How strict each directory is

The rules each directory states, by what happens when a plugin breaks one. A block stops the submission, a hold sends it to a reviewer, and a warning lets it through.

Claude plugin directory23 rules: 14 blocking, 7 held for review, 2 warnings
ChatGPT and Codex plugin directory8 rules: 7 blocking, 1 held for review, 0 warnings
Cursor Marketplace7 rules: 6 blocking, 0 held for review, 1 warning

BlocksHeld for reviewWarning

What a reviewer decides

Each directory also checks things no packaging rule can settle before you submit.

Claude plugin directory: Whether another organization already uses the name, and brand look-alikes.
Claude plugin directory: The security scan that runs after you submit, and the Anthropic Software Directory Policy.
ChatGPT and Codex plugin directory: Listing fields entered in the portal: display name, short description, category, support and privacy URLs, test cases.
ChatGPT and Codex plugin directory: Domain verification and review of the MCP server.
Cursor Marketplace: Name uniqueness and the manual security review of every version.

Questions about Claude Code, Codex and Cursor plugins

Which has more plugins, Claude Code, Codex or Cursor?

Claude Code, with 710 plugins in the HOL catalog, then Codex with 552 and Cursor with 216. The counts come from the runtimes each listing declares.

Can one plugin work in Claude Code, Codex and Cursor?

Yes. Each runtime reads its own manifest, so one repository can carry .claude-plugin/plugin.json, .codex-plugin/plugin.json and .cursor-plugin/plugin.json side by side. 367 plugins declare both Claude Code and Codex (51.7% of Claude Code plugins), and 184 declare both Claude Code and Cursor.

Can a Codex plugin use lifecycle hooks?

Not in the public directory. Plugins with lifecycle hooks are not eligible for the public directory; ship a version without hooks.

How many MCP servers can a Codex plugin have?

One. Only one MCP server can be connected per plugin. Use a stable public https URL; local servers go through the desktop-only route.

Do Cursor Marketplace plugins have to be open source?

Yes. All Marketplace plugins must be open source; add a LICENSE file.

What does the Claude plugin directory check that the others do not?

File and package hygiene. It blocks unpinned npx and uvx launchers, symbolic links, system files and oversized repositories, and holds plugins with more than 512 files or binary files for review. Codex and Cursor list no such rules on the pages HOL reads.

Plugin pre-flight: run these rules against your repository before you submit.
Claude Code plugin converter: write the Codex and Gemini CLI manifests for a Claude Code plugin.
Publish a Claude Code plugin to Codex, Cursor and Gemini CLI: the step-by-step guide.
Runtime compatibility map: every pair of runtimes in the catalog, not just these three.
Browse Claude Code plugins
Browse Codex plugins
Browse Cursor plugins