Summary

Splits the monolithic cloudflare plugin into 9 plugins (8 product plugins + 1 umbrella) per the request in #50. Existing users keep working transparently — on Claude Code via the umbrella's plugin dependencies, on Cursor via an inverted-symlink layout that keeps the root cloudflare plugin functional. Users who want narrower scope and lower per-session token usage can install only the per-product plugins they need.

What changed

The marketplace ships these plugins (canonical content under plugins/<plugin-name>/):

Each MCP server lives in exactly one plugin. Other plugins reach those MCPs transitively via the dependency tree. (Verified empirically: Claude Code silently dedupes duplicate MCP server names across plugins, so duplicating servers across plugins is unsafe.)

No skill, command, or rule content has changed — all files are pure git renames into plugins/<plugin-name>/. The only content additions are the new manifests.

Cursor monolith continuity (inverted-symlink layout)

Cursor's plugin system has no plugin-to-plugin dependency mechanism (verified against the Cursor docs and the cursor/plugins repo — none of the 11 official plugins declare dependencies, and the Plugins Reference doesn't list a dependencies field). The Claude umbrella pattern doesn't translate.

To keep existing cloudflare@cloudflare Cursor installs working without forcing a migration, the repo root keeps a thin "Cursor monolith" plugin layout that resolves into the per-product plugins via symlinks:

• skills/<X> → ../plugins/<product>/skills/<X> (8 skill symlinks)
• commands/<X>.md → ../plugins/<product>/commands/<X>.md (2 command symlinks)
• rules/workers.mdc → ../plugins/cloudflare-workers/rules/workers.mdc (1 rule symlink)
• .cursor-plugin/plugin.json — the Cursor monolith manifest (unchanged from upstream)
• .cursor-plugin/marketplace.json — re-adds cloudflare → ./ alongside the 8 per-product entries
• .mcp.json — hand-merged from the 3 product .mcp.json files (5 servers, identical to upstream pre-PR)

Symlinks point inside the Cursor monolith plugin's source dir (./), satisfying the empirically-verified "internal symlinks are preserved through git clone" constraint. Claude Code never scans the repo root, so the Claude umbrella plugin (deps-only at plugins/cloudflare/) is unaffected — content is loaded once via the per-product plugins, not twice.

The root .mcp.json is hand-maintained: when a product's .mcp.json changes, the root file needs to be updated to match. The README's "Repository layout" section documents this for contributors.

Migration: Claude Code (smooth)

The new cloudflare umbrella plugin depends on all 8 product plugins. Existing users running /plugin install cloudflare@cloudflare get the same content as before, transparently — Claude Code auto-installs the 8 dependencies. No user action required.

Users who want lower per-session token usage can uninstall the umbrella and install only the product plugins they need:

/plugin uninstall cloudflare@cloudflare
/plugin install cloudflare-workers@cloudflare

Installing cloudflare-workers automatically pulls in cloudflare-core via the dep graph.

Migration: Cursor (smooth)

Existing Cursor users with the cloudflare monolith plugin keep working — same skills, same MCP servers, same install path. No user action required.

Users who want narrower scope can install per-product Cursor plugins from the same marketplace. Note that without dependency resolution, each Cursor plugin ships only its own MCP servers — installing only cloudflare-workers gives cloudflare-bindings and cloudflare-builds but not cloudflare-api/cloudflare-docs/cloudflare-observability. Users who want the full MCP surface should keep the cloudflare umbrella.

Verification

• All 9 plugin manifests pass claude plugin validate.
• End-to-end tested locally:
  • claude plugin install cloudflare@cloudflare → installs umbrella + auto-installs 8 dependencies.
  • claude plugin install cloudflare-workers@cloudflare (without the umbrella) → installs only cloudflare-workers + cloudflare-core (transitive).
  • All 5 MCP servers connect with proper plugin namespacing (plugin:cloudflare-core:cloudflare-api, etc.).
• Cursor install pipeline preserves internal symlinks: empirically verified that a git clone --depth 1 of this branch produces a working tree where the 11 root symlinks are intact (mode-120000), and Cursor's runtime loader follows them when scanning <plugin-root>/skills/*/.
• Git rename detection auto-merges upstream edits to moved files even with the co-located symlink ADD at the original parent path (verified on scratch repos before authoring this restructure).

Open questions for maintainers

1. .mcp.json vs mcp.json for Cursor. The repo uses .mcp.json (Claude Code convention). Cursor's plugin docs document mcp.json (no leading dot) as the auto-discovery filename. Today the repo uses .mcp.json and apparently works for both ecosystems, but if Cursor's auto-discovery actually needs mcp.json for plugin-scoped configs, please let me know and I'll either rename the files or add an explicit mcpServers: "./.mcp.json" to each Cursor manifest.
2. Per-plugin logos. The Cursor monolith plugin.json references logo.svg at the repo root, which still works (the file is present). Per-product Cursor plugins don't reference a logo because plugin source paths can't reach files outside the plugin's own directory after install. Happy to duplicate logo.svg into each plugin if branding consistency matters.
3. Hand-merged root .mcp.json. The 5 server entries are duplicated between the root file and the 3 product .mcp.json files. Tolerable as long as MCP server adds/removes are infrequent. A future PR could add a CI check that asserts the union matches the root if drift becomes a concern.
4. PR scope. Both Claude Code and Cursor manifests update in lockstep here, since moving files out of the repo root affects both ecosystems simultaneously. If you'd prefer them in separate PRs anyway, I can split.

Test plan

• Maintainer reviews the partition (which skills/commands/MCPs go in which plugin).
• Maintainer confirms .mcp.json filename works for Cursor plugin auto-discovery (or asks for mcp.json).
• Smoke-test on Claude Code: install umbrella, confirm everything loads as before.
• Smoke-test on Claude Code: install only cloudflare-workers, confirm transitive cloudflare-core install and that observability MCP is NOT loaded.
• Smoke-test on Cursor: install the cloudflare umbrella, confirm all 8 skills + 5 MCP servers load (matches pre-PR behavior).
• Smoke-test on Cursor: install one or more per-product plugins, confirm narrower scope works as expected.

Closes #50

🤖 Generated with Claude Code