What
- Adding a marketplace from a link or URL, whether via
/plugin marketplace add <path/url>or by installing a plugin from a link, now carries aconfirmAddpayload. The add-marketplace screen automatically shows a confirmation step when this hasn't been set yet but a link-based source was provided. - A new
install-from-sourceaction routes to the add-marketplace screen with plugin and link-origin details for this confirmation step. - A new
usage-errorfallback routes back to the plugin menu instead of failing silently. - Installing now short-circuits to an npm-install path when the target parses as a
plugin@npmspec.
Why
This adds a safety check before trusting and adding a marketplace source from an arbitrary link, and cleans up how installs from different kinds of sources (links, npm packages, usage errors) are routed.
Names in the bundle/plugin marketplace add
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Troubleshoot plugins touched a line naming /plugin marketplace add after this was published.
You ran `/plugin marketplace add <source>`, `claude plugin marketplace add <source>`, or `claude plugin install <plugin> --marketplace <source>`, and Claude Code replied `Invalid marketplace source format. Try: owner/repo, https://..., or …plugins/troubleshooting see the edit
Confirmed since
Anthropic's documentation has since written up /plugin marketplace add, on Get started with MCP Apps.
/plugin marketplace add modelcontextprotocol/ext-appsconnectors/building/mcp-apps/getting-started see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /plugin marketplace add, on Get started with MCP Apps.
Anthropic's release notes agree
Added /plugin install <plugin> --marketplace <source>, which offers to add the marketplace before installing the plugin