Read the whole setupGet the setup that works.
Drop your email and unlock the rest: what you need, the exact install and uninstall commands, the scope choice that matters, and how to review a plugin before trusting it.
One email. No follow-up unless I ship something that fits.
WHAT YOU NEED- Claude Code, already installed and authenticated
- Nothing else for most plugins, they arrive pre-configured
- A language-server binary, only for the code-intelligence plugins, installed separately per language
INSTALLOne command, once you know the name
Browse first if you are not sure of the exact plugin name. The install itself is one line either way.
The install
claude code sessionexample: GitHub integration
/plugin install github@claude-plugins-official → or browse first: /plugin, then the Discover tab
The install screen shows a context-cost estimate and the exact commands, skills, agents, hooks and MCP servers it will add, before you confirm anything.
Prove itAfter install, run /plugin list --enabled and confirm the new plugin appears. If it does not, run /reload-plugins once.
CONFIGUREScope is the one real decision
Every install asks where it applies. Get this wrong and a plugin either leaks into repos it should not touch, or never reaches the teammates who need it.
install scopepick one
User scope → yours, across every project Project scope → shared with collaborators via .claude/settings.json Local scope → yours, this repo only, never shared
| Setting | Default | Why I change it |
|---|
| Scope | asked at install | User scope for a personal tool like commit-commands. Project scope for anything the whole team should get automatically. |
| Auto-update | on for this marketplace | Leave it on for official plugins. Flip it off per-marketplace only for a third-party catalog you want to pin. |
Reviewing before trustThe Discover tab's detail pane lists every command, skill, agent, hook and MCP server a plugin adds. Read that list before installing anything that touches credentials or a production system.
DAILY DRIVINGManage what is already installed
The same handful of commands cover almost everything you will do after the first install.
- List what you have.
/plugin list shows everything installed; add --enabled or --disabled to filter. - Disable without losing config.
/plugin disable plugin-name@marketplace-name turns it off without uninstalling, useful when troubleshooting a conflict. - Remove it cleanly.
/plugin uninstall plugin-name@marketplace-name takes it out completely.
Closing the /plugin menu after a change runs /reload-plugins for you automatically in most cases.
WHEN IT DRIFTSTwo failures, both configuration
A plugin's skills do not appear
Run /reload-plugins, or if that does not fix it, clear the cache with rm -rf ~/.claude/plugins/cache, restart, and reinstall.
An LSP plugin reports Executable not found
The language-server binary itself is missing. Install it from the table on the official docs, the plugin never installs the binary for you.
If the marketplace itself is missing/plugin marketplace add anthropics/claude-plugins-official re-registers it, then retry the install.
THE SHAPE OF ITWhere everything lives
/pluginsinternal plugins developed and maintained by Anthropic /external_pluginsthird-party plugins that passed Anthropic's review for this catalog ~/.claude/plugins/cacheyour local cache; safe to clear if a plugin misbehaves .claude/settings.jsonwhere a project-scope install actually lives
Uninstalling a marketplace removes every plugin you installed from it, so remove individual plugins first if you only want to trim, not start over.
That is the whole setupOne command per plugin, a scope choice that actually matters, and the MCP servers you used to wire by hand show up pre-configured instead. Read what a plugin adds before you trust it, official catalog or not.
Open on GitHub →
↑ Unlocks the moment you submit the form above.
