How to List, Inspect, and Remove Claude Code Plugins and Marketplaces

Claude Code plugins add features such as skills, agents, hooks, and connections to external tools. A marketplace is a catalog of plugins that tells Claude Code where to get them. Removing a plugin leaves its marketplace registered; removing a marketplace can also uninstall plugins installed from it.

Use claude plugin list or the /plugin panel to check what is available. Before removing a plugin, inspect its components and source, then choose the correct uninstall scope. Scope means where Claude Code applies a plugin setting: across your account, for everyone using a project, or only for you in one project.

List installed plugins and registered marketplaces

From a shell, run:

claude plugin list

The command reports plugin versions, scopes, and statuses. Its output can also include plugins that a flag loads only for the current session, plugins found in a skills directory, and plugins synced from claude.ai. Check each entry’s category and scope before treating it as a standard marketplace installation. The plugin command reference describes these output categories.

In an interactive Claude Code session, enter /plugin and open the Installed tab. The panel shows installed plugins and their scopes, and provides options to manage them. The plugin installation and management documentation describes the panel and its controls.

To list configured marketplaces from a shell, run:

claude plugin marketplace list

To see structured source information, use:

claude plugin marketplace list --json

The output can include a marketplace’s registered name, source type, repository or URL, local path, pinned branch or tag, and cache location. Use the registered name shown in the list when you remove a marketplace; it may not match the repository or URL you used to add it. Options can vary by Claude Code version, so check claude plugin marketplace list --help if a flag is unavailable.

Inspect a plugin and its source

To inspect a plugin Claude Code has made available for use, run:

claude plugin details 

Claude Code reports the plugin’s components and projected token cost. Claude Code makes a plugin available when it is installed, appears in a skills directory, or is supplied with a plugin-loading flag. You can also open a plugin’s details from the /plugin panel.

To inspect a plugin before installing it, open /plugin and select the Marketplaces tab. Choose a marketplace, then browse its plugins. The Discover tab lists plugins from configured marketplaces. Details can show what a plugin installs, such as skills, commands, agents, hooks, and servers. Hooks run in response to Claude Code events; MCP servers connect Claude Code to external tools or data. Review these components and the plugin’s code when evaluating what it will do. A marketplace listing describes a plugin, but does not establish that its code is safe.

You can also inspect the marketplace catalog and plugin metadata files. The marketplace catalog is in .claude-plugin/marketplace.json; plugin metadata can be in .claude-plugin/plugin.json. The marketplace structure documentation explains these files. Metadata shows which components and sources the plugin declares, but you still need to inspect the code those components run.

Choose the right scope when uninstalling

Claude Code uses three ordinary plugin scopes:

To uninstall a plugin from a specific scope, run:

claude plugin uninstall @ --scope user

Replace user with project or local to target a different scope. Use the plugin ID shown by claude plugin list; it commonly has the form name@marketplace. The command defaults to user scope, so naming the scope explicitly helps avoid removing the wrong installation. The CLI reference documents the uninstall command and scope options.

In the interactive session, open /plugin, find the plugin under Installed, open its details, and choose Uninstall. If a shared project setting enables the plugin, Claude Code can ask whether to disable it just for you or remove the shared setting for everyone using the project. Choose based on whether you want to change your own configuration or the repository’s shared configuration.

Disabling a plugin turns it off while leaving it installed. Uninstalling removes it from the selected scope. Organization-managed plugins and plugins synced from claude.ai have separate control paths, so an individual user may not be able to remove them through the ordinary uninstall command.

Uninstalling a plugin does not necessarily remove dependencies that no remaining plugin uses. Run claude plugin prune to remove unused, auto-installed dependencies. The command does not remove plugins you installed yourself.

Remove a marketplace only when you want to remove its plugins too

Remove a marketplace with its registered name:

claude plugin marketplace remove 

You can also run /plugin marketplace remove <marketplace-name> in an interactive session. Without a scope flag, the CLI removes the marketplace declaration from all scopes. If no declaration remains in another scope, Claude Code removes the marketplace cache and uninstalls plugins installed from it. It also removes saved options, secrets, and data where it can. In the interactive panel, Claude Code identifies affected plugins before asking you to confirm.

If you want to keep the marketplace and its installed plugins but refresh its catalog, run:

claude plugin marketplace update 

Marketplace removal has broader effects than uninstalling one plugin. Confirm the registered name and review which plugins will be affected before proceeding. Organization-managed marketplaces can be governed by policy, which can limit what you can remove yourself.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com