Ext Ops Panel
Open dashboard
Comparison

Cursor SDK vs Chrome Extension Builder

Cursor SDK is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). Chrome Extension Builder is a plugin bundle for AI coding tools published by harry-harish. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceCursor SDKChrome Extension Builder
Cursor: cursor/plugins Listed
Version: 1.0.0
Forks (GitHub): 1 066
Stars (GitHub): 11 026
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.4.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Cursor SDK vs Chrome Extension Builder
FactCursor SDKChrome Extension Builder
Marketplaces that list it11
Stars (GitHub) (differs)11 026 (better)1 (worse)
Forks (GitHub) (differs)1 066 (better)0 (worse)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published3
Parts of the bundle (differs)119
LicenceMITMIT
Repository (differs)github.com/cursor/pluginsgithub.com/harry-harish/chrome-extension-builder
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Cursor SDK

In its own words, on Cursor: cursor/plugins:

Build apps, scripts, and automations with the TypeScript SDK.

Chrome Extension Builder

In its own words, on Claude Code: claude-plugins-community:

Use when scaffolding, validating, testing, or publishing a Manifest V3 Chrome/Edge/Firefox extension. Builds end-to-end with WXT, Plasmo, or CRXJS — service-worker dispatcher, typed message passing, strict CSP, _locales/ i18n, Playwright smoke harness, Chrome Web Store submission prep.

How to run each

Cursor SDK

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Chrome Extension Builder As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install chrome-extension-builder@claude-community

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Cursor SDK · What it can do: Chrome Extension Builder · Compare two other plugins

Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built