Find the official catalog first
For official Claude Code plugins, start with anthropics/claude-plugins-official. In an interactive Claude Code session, open /plugin and browse Discover. Check the plugin's author and components before choosing an installation scope.
The marketplace includes Anthropic-maintained plugins and external contributions. Its name alone does not mean that Anthropic wrote every entry. A plugin may also need a separate executable, service account or MCP configuration before its features work.
This guide covers Claude Code on a local machine. It does not treat installing a Claude Code plugin as installing an extension into Claude chat or Cowork. The current installation documentation explains the supported surfaces separately.
Distinguish a plugin, a skill and an MCP server
| Item | What to inspect | What installation does not establish |
|---|---|---|
| Plugin | Manifest, author, bundled components and marketplace | That every component is ready or appropriate for your project |
| Skill | Its instructions, inputs and requested actions | That it supplies a running external service |
| MCP server | Executable or endpoint, configuration and authentication | That a model can use it successfully with your account |
A plugin is a distribution package: it can include skills, agents, hooks and server configurations. A skill provides task instructions. An MCP server exposes tools or resources through a connection. These can work together, but checking one does not validate the others.
For a standalone skill, use the existing Taste Skill installation guide. For MCP JSON, the local configuration checker can inspect structure without uploading the input. It does not start a server or prove that credentials work.
Choose the smallest useful scope
The scope controls where the plugin is enabled. Choose it before installing, especially when experimenting in a repository shared with other people.
| Scope | Typical use | Settings location |
|---|---|---|
user |
Your projects on this machine | ~/.claude/settings.json |
project |
A repository's shared configuration | .claude/settings.json |
local |
Your use in one repository | .claude/settings.local.json |
A project setting is something collaborators can review and commit. It is not evidence that every collaborator already downloaded the plugin. For a first check, a disposable directory and local scope make the resulting changes easier to inspect.
Install from the shell and read back the result
First check the installed CLI:
claude --version
claude plugin install --help
claude plugin marketplace list
If the official marketplace is absent, register it once:
claude plugin marketplace add anthropics/claude-plugins-official
Then install a known entry with an explicit scope. The example below uses commit-commands, which the official documentation also uses. Review its commands before invoking any of them: some can change commits, branches or remotes.
claude plugin install commit-commands@claude-plugins-official --scope local
claude plugin list --json
Our isolated macOS test used Claude Code 2.1.193 and the official marketplace checkout d1adba47161a. The install command exited successfully. The listing reported the expected plugin ID, scope: local, and enabled: true. The cache version was a commit identifier rather than a conventional release number.
Those are installation-state checks. We did not run the plugin's commit, push or cleanup commands, make a model request, or test a third-party server. The temporary test used a separate Claude configuration directory; hashes of the user's real settings stayed unchanged.
Confirm availability in the session
After a shell installation, start a new Claude Code session in the same directory, or use the reload action documented for your installed version. Open the Installed tab in /plugin and compare its scope with the shell listing.
The documentation identifies namespaced commands such as /commit-commands:commit. Finding an entry is the next check; executing it is a separate action. Review the repository status and the command's requested behavior before allowing it to modify anything. Our test did not establish successful command execution in an authenticated model session.
If the plugin is listed but unavailable, compare the current working directory, scope and enabled state. If a bundled server asks for setup, complete that server's documented configuration rather than repeatedly reinstalling the whole plugin. Keep the exact error and CLI version when asking for help.
Disable, re-enable or remove the same scoped installation
Use the same plugin ID and scope throughout the lifecycle:
claude plugin disable commit-commands@claude-plugins-official --scope local
claude plugin list --json
claude plugin enable commit-commands@claude-plugins-official --scope local
claude plugin list --json
claude plugin uninstall commit-commands@claude-plugins-official --scope local
claude plugin list --json
In the reproduced test, disabling changed enabled to false, enabling restored true, and the final listing after uninstall was empty. No plugin commands were invoked during those checks. Removing this one installation is different from deleting a marketplace or disabling all plugins.
The CLI reference documents the management commands. Its newest options may be newer than your binary, so use local --help before copying optional flags. If another scope still enables the same plugin, inspect that declaration before assuming the uninstall failed. Avoid deleting the entire Claude settings directory to repair a single entry.