[franco-zalamena-iterable]

Fix the Cursor install steps, and stop bundling the unused Context7 MCP server

People following the README's Cursor steps couldn't get the plugin installed. This PR rewrites the Cursor part of the README to match Cursor's current docs and the current Cursor app.

It also stops the plugin from installing the Context7 MCP server, which no skill uses. That's the one shipped change, so the plugin goes to 26.10.9-beta.

What was wrong with the old steps

• The steps treated the GitHub import as the install. In Cursor, + Add → From GitHub Repository opens an Import Marketplace dialog. That dialog has a Repository field, a Scope choice (User or Team) and an Import button. The import adds the repository as a marketplace in the user's Cursor account. The plugin is then installed from that marketplace as a separate step. The old step 3 ("Enter the URL") left out the dialog and the Import button. The old step 4 ("Find iterable-sdk") didn't say where to look. Until it's installed, the plugin is not in the Plugins list.
• Plan differences were missing. Cursor's plan comparison lists Community plugin import as on by default on Teams and off by default on Enterprise. On Enterprise, only admins can add team marketplaces.
• The local-plugin note was out of date. It said Teams and Enterprise both need an admin to allow local imports. The docs now say Allow Local Plugin Imports is an Enterprise control, and it's off by default there.
• There was no way to confirm the install. Nothing said what a working install looks like.
• The "3.9 or later" minimum isn't backed by the docs for this flow. Customize launched in 3.9, but no doc says which version added the Customize GitHub import. The README now says to update to the latest version.

Corrected flow

Free and Pro (individual):

1. Sign in, then open Customize → Plugins.
2. Select + Add → From GitHub Repository.
3. In Import Marketplace, paste the repository URL under Repository. Keep Scope: User and select Import.
4. Cursor switches to the marketplace browser. Select Personal or Iterable, whichever the marketplace is listed under, to see its plugins, then open iterable-sdk.
5. On the plugin's page, select Install. If Cursor asks for a scope, choose the project or user scope.

To confirm, open Customize: Plugins lists iterable-sdk, and Skills lists the six skills.

Teams: the same steps work, because community plugin import is on by default. An admin can instead share the plugin through a team marketplace: Dashboard → Plugins & MCPs → Team Marketplaces → Add Marketplace → Import from Repo, then Add to Marketplace, then Marketplace Settings → Marketplace Access. The admin then picks Default Off, Default On or Required for the plugin. The Teams plan allows one imported team marketplace. Auto Refresh needs the Cursor GitHub App on the source repository, so admins should use Refresh.

Enterprise: community plugin import is off by default. An admin has to allow it, or add the repository as a team marketplace. Local imports need Allow Local Plugin Imports under Dashboard → Settings → Security & Identity → Marketplace and Plugins.

Other notes now in the README:

• Cursor also loads a copy of the plugin installed in Claude Code while Include Third-Party Plugins, Skills, and Other Configs is on.
• A marketplace install takes precedence over a local copy with the same name.

The Updating and Uninstalling sections now describe the marketplace too: refresh it or re-import it to update, and remove it from the account to uninstall.

Stop bundling the Context7 MCP server

The plugin shipped mcp.json and .mcp.json, which registered Context7's MCP server in every Cursor and Claude Code install, so Cursor listed context7 under MCPs. No skill calls it. The skills answer from the docs they ship in reference/, and iterable-android tells agents not to reach for Context7.

The server was a third-party tool in every install that an agent could query instead of the shipped docs, and one an organization may have to approve. This PR:

• deletes both files;
• removes the pipeline/src/validate-plugins.ts rule that required mcpServers.context7;
• removes the matching check in tests/plugin-manifests.sh;
• removes the README's Context7 lines.

The context7.json library listing stays, so anyone using Context7 on their own can still look these docs up as /iterable/iterable-sdk-skill. On their next update, existing installs lose the server.

Manifests

• cursor/plugin-template's scripts/validate-template.mjs passes on this branch. Its only output is two expected warnings: there's no hooks/hooks.json and no mcp.json ("only needed when using MCP servers").
• The current Cursor app's manifest schema and component discovery accept .cursor-plugin/plugin.json and .cursor-plugin/marketplace.json as they are. This includes source: "./", and the skills array of individual skill folders (an array entry that holds its own SKILL.md is read as a skill).
• The template README says a single plugin can drop marketplace.json. Don't do that here: Cursor's docs say the Customize GitHub import needs .cursor-plugin/marketplace.json.
• The version: deleting the MCP files is a shipped change, so the version goes to 26.10.9-beta. Two other pending changes use 26.10.7-beta and 26.10.8-beta, and whichever merges later needs a re-bump.

How it was tested

• tests/run-all.sh: 49 suites and 992 checks passed, with 0 failures. Two live-project suites skipped, and the two network suites weren't run.
• pipeline/src/validate-plugins.ts passes, and so does tsc --noEmit.
• cursor/plugin-template's validator passes. It gives only the two expected warnings: there's no hooks file and no mcp.json.
• tools/install-local no longer expects the MCP files in an export. tests/install-local.sh caught that.
• The main install path was checked in the live Cursor app, as described under "Confirmed in the live UI".

Sources

All Cursor pages were fetched on 2026-10-23. Unless a version is given below, the page showed no date.

• Cursor docs through Context7 (/websites/cursor), cross-checked against the live pages.
• https://cursor.com/docs/plugins: Installing plugins, Team marketplaces, Add a team marketplace, Keep plugins up to date, Where developers find team marketplaces, Test plugins locally.
• https://cursor.com/docs/skills and https://cursor.com/docs/rules, "Installing skills from a repository": "import the repository in Customize with From GitHub Repository (the repository needs a .cursor-plugin/marketplace.json) … then install the plugin."
• https://cursor.com/docs/reference/plugins: manifest fields and component discovery.
• https://cursor.com/docs/enterprise, Plan Comparison → Marketplace: Community plugin import: Teams "On by default", Enterprise "Off by default".
• https://cursor.com/docs/reference/third-party-hooks: Include Third-Party Plugins, Skills, and Other Configs in Cursor Settings → Agents → Third-Party Imports, on by default.
• https://cursor.com/docs/cli/changelog, May 7, 2026: "Plugins imported from Claude Code appear alongside native ones."
• https://cursor.com/docs/release-notes/ide, 3.19: plugin pages and the Install button.
• https://cursor.com/changelog/customize: 3.9, June 22, 2026.
• The Cursor 3.26.16 desktop app's UI strings. These confirm the labels Add, From GitHub Repository, Import Marketplace, Repository, Scope, User/Team, Import, Add to Cursor, Add Marketplace, Import from GitHub, Uninstall and "Remove marketplace?". They also show that the import calls an account-level "add marketplace" request, and that the marketplace view opens afterwards.
• cursor/plugin-template at commit 4621607 (2026-04-24).

Confirmed in the live UI

After Import, Cursor shows the marketplace browser; the plugins appear once you select Personal or Iterable. The plugin page's button reads Install.

Still to check in the live UI

The README marks each of these with <!-- verify in UI -->:

1. Whether you need to be signed in, and the lowest Cursor version that shows From GitHub Repository.
2. The other entry point: Add Marketplace → Import from GitHub in the marketplace view.
3. Where an Enterprise admin allows community plugin import. The docs list the default but not the setting's location.
4. That a copy installed in Claude Code loads through Third-Party Imports.
5. How to refresh or remove a personal marketplace from Customize.

🤖 Generated with Claude Code