How to Install and Discover Claude Code Plugins Through Marketplaces in 2025

How to Install and Discover Claude Code Plugins Through Marketplaces in 2025

Plugin marketplaces enable developers to extend Claude Code with pre-built commands, agents, and integrations without building custom extensions. Users add marketplace catalogs to Claude Code, browse available plugins, and install specific tools for code intelligence, external integrations, or workflow automation. The official Anthropic marketplace comes pre-configured, while third-party marketplaces require manual addition using GitHub repositories, Git URLs, or local paths.

Key Takeaways

• Marketplaces function as catalogs that register with Claude Code separately from plugin installation—adding a marketplace grants browsing access without installing any tools
• Three installation scopes determine plugin availability: user scope (all projects), project scope (shared with collaborators), or local scope (current repository only)
• Official marketplace includes LSP-based code intelligence plugins for 10 languages including Python, TypeScript, Rust, and Go, requiring language server binaries
• Plugin commands use namespaced syntax like /commit-commands:commit to prevent conflicts between extensions
• Auto-update settings refresh marketplace data and installed plugins at startup for official marketplaces by default

Introduction

Claude Code's plugin system transforms the AI coding assistant into a customizable development environment. Developers face a common challenge: extending tools without building complex integrations from scratch. Plugin marketplaces solve this problem by providing curated collections of pre-built extensions.

The marketplace architecture separates discovery from installation. Users register catalogs to browse available plugins, then selectively install tools matching their workflow needs. This two-step process prevents unwanted installations while maintaining easy access to new capabilities.

What Are Claude Code Plugin Marketplaces?

Plugin marketplaces serve as catalogs of extensions created and shared by developers. Marketplaces contain plugins that add custom commands, agents, hooks, and Model Context Protocol (MCP) servers to Claude Code.

The system distinguishes between marketplace registration and plugin installation. Adding a marketplace registers the catalog for browsing without installing any plugins. Users then select individual plugins from registered marketplaces for installation.

The official Anthropic marketplace (claude-plugins-official) comes pre-configured with Claude Code. Additional marketplaces require manual addition through the /plugin marketplace add command.

How Do You Add Plugin Marketplaces to Claude Code?

GitHub Repository Marketplaces

Add GitHub-hosted marketplaces using the owner/repo format:

/plugin marketplace add anthropics/claude-code

The repository must contain a .claude-plugin/marketplace.json file at its root. Claude Code downloads the catalog and makes plugins available for browsing.

Git URL Marketplaces

Add marketplaces from any Git host using full URLs:

• HTTPS format: /plugin marketplace add https://gitlab.com/company/plugins.git
• SSH format: /plugin marketplace add git@gitlab.com:company/plugins.git
• Specific branches: Append #branch-name or #v1.0.0 for tags

Local and Remote Path Marketplaces

Install from local directories or direct URLs:

• Local directory: /plugin marketplace add ./my-marketplace
• Direct JSON file: /plugin marketplace add ./path/to/marketplace.json
• Remote URL: /plugin marketplace add https://example.com/marketplace.json

What Plugin Categories Does the Official Marketplace Offer?

Code Intelligence Plugins

Code intelligence plugins implement the Language Server Protocol (LSP) for deep codebase understanding. These plugins enable Claude to jump to definitions, find references, and display type errors immediately after edits.

Available LSP plugins require corresponding binaries:

Claude Code prompts users to install the corresponding plugin when opening projects with detected language servers.

External Integration Plugins

Integration plugins bundle pre-configured MCP servers for external services:

• Source control: github, gitlab
• Project management: atlassian (Jira/Confluence), asana, linear, notion
• Design tools: figma
• Infrastructure: vercel, firebase, supabase
• Communication: slack
• Monitoring: sentry

Development Workflow Plugins

Workflow plugins add specialized commands and agents:

• commit-commands: Git commit workflows including staging, commit message generation, and PR creation
• pr-review-toolkit: Specialized agents for pull request reviews
• agent-sdk-dev: Tools for building with Claude Agent SDK
• plugin-dev: Toolkit for creating custom plugins

Output Style Plugins

Customization plugins modify Claude's response format:

• explanatory-output-style: Educational insights about implementation choices
• learning-output-style: Interactive learning mode for skill building

How Do You Install and Manage Plugins?

Installation Process

Run /plugin to open the plugin manager interface with four tabs:

1. Discover: Browse available plugins from all registered marketplaces
2. Installed: View and manage installed plugins
3. Marketplaces: Add, remove, or update marketplace registrations
4. Errors: View plugin loading errors

Select a plugin in the Discover tab to view details and choose an installation scope.

Installation Scopes

Claude Code offers three installation scopes:

• User scope: Installs for the current user across all projects (default)
• Project scope: Installs for all collaborators via .claude/settings.json in the repository
• Local scope: Installs for the current user in the specific repository only

Command-line installation uses user scope by default:

/plugin install plugin-name@marketplace-name

Specify alternative scopes with the --scope flag:

claude plugin install formatter@your-org --scope project

Plugin Management Commands

Manage installed plugins through direct commands:

• Disable: /plugin disable plugin-name@marketplace-name
• Enable: /plugin enable plugin-name@marketplace-name
• Uninstall: /plugin uninstall plugin-name@marketplace-name

The Installed tab groups plugins by scope for easy management. Enterprise-managed plugins appear with managed scope and cannot be modified by users.

How Do Auto-Updates Work for Marketplaces?

Claude Code automatically updates marketplaces and installed plugins at startup when auto-update is enabled. The system refreshes marketplace data and updates plugins to their latest versions, displaying a notification when updates occur.

Auto-update defaults:

• Official Anthropic marketplaces: Enabled by default
• Third-party marketplaces: Disabled by default
• Local development marketplaces: Disabled by default

Toggle auto-update through the plugin manager:

1. Run /plugin to open the interface
2. Select the Marketplaces tab
3. Choose a marketplace
4. Select "Enable auto-update" or "Disable auto-update"

Set the DISABLE_AUTOUPDATER environment variable to disable all automatic updates for Claude Code and plugins.

Unique Perspective

The marketplace architecture reveals a deliberate design philosophy: separation of discovery from installation prevents bloat while maintaining accessibility. The three-scope installation system addresses a critical tension in development tools—balancing individual customization with team standardization. User scope enables personal workflow optimization, project scope ensures team consistency, and local scope allows repository-specific experimentation without affecting other projects. This granular control prevents the common problem of tool sprawl where teams accumulate incompatible configurations. The LSP integration strategy demonstrates pragmatic reuse—leveraging existing language server infrastructure rather than building proprietary solutions. Organizations can create private marketplaces for internal tools while still accessing public marketplaces, enabling hybrid extension strategies that combine open-source and proprietary capabilities.

FAQ

What version of Claude Code supports plugins?

Plugins require Claude Code version 1.0.33 or later. Check your version with claude --version in the terminal. Update through Homebrew (brew upgrade claude-code), npm (npm update -g @anthropic-ai/claude-code), or by re-running the native installer. Restart your terminal after updating to access the /plugin command.

Can you install plugins without adding marketplaces first?

The official Anthropic marketplace comes pre-configured with Claude Code, allowing immediate plugin installation without additional setup. Third-party plugins require adding their marketplace first using /plugin marketplace add followed by the repository or URL. The marketplace registration makes plugins available for browsing and installation.

What happens when you remove a marketplace?

Removing a marketplace with /plugin marketplace remove marketplace-name automatically uninstalls all plugins installed from that marketplace. The marketplace catalog disappears from the Discover tab, and associated plugins no longer function. Users must reinstall plugins if they re-add the marketplace later.

How do plugin commands differ from standard Claude commands?

Plugin commands use namespaced syntax with the format /plugin-name:command-name to prevent conflicts between extensions. For example, the commit-commands plugin provides /commit-commands:commit rather than just /commit. This namespacing allows multiple plugins to offer similar functionality without command collisions.

Do code intelligence plugins work without language servers?

Code intelligence plugins require corresponding language server binaries installed on your system. Installing the plugin without the binary generates an "Executable not found in $PATH" error in the Errors tab. Install the required binary (like pyright-langserver for Python) before the plugin functions properly.

Can team members share plugin configurations?

Project scope installation adds plugins to .claude/settings.json in the repository, sharing the configuration with all collaborators. Team members receive prompts to install these plugins when they trust the repository folder. User scope and local scope installations remain private to individual developers.

What security considerations apply to third-party plugins?

Anthropic does not control or verify third-party plugin contents, including bundled MCP servers, files, or software. Users should review each plugin's homepage and source code before installation. Only install plugins from trusted sources, especially those requiring external service connections or file system access.

How do you troubleshoot plugins that fail to load?

Check the Errors tab in the plugin manager (/plugin command) for specific error messages. Common issues include missing language server binaries, inaccessible plugin source URLs, or cache corruption. Clear the plugin cache with rm -rf ~/.claude/plugins/cache, restart Claude Code, and reinstall affected plugins.

Take Action on Plugin Marketplaces

Plugin marketplaces transform Claude Code from a general AI assistant into a specialized development environment tailored to your workflow. Start by exploring the official Anthropic marketplace with /plugin, then add the demo marketplace (anthropics/claude-code) to see advanced capabilities.

Install code intelligence plugins for your primary programming languages to enable definition jumping and type checking. Experiment with workflow plugins like commit-commands to automate repetitive development tasks.

Next step: Run /plugin marketplace add anthropics/claude-code to access the demo marketplace and install your first workflow automation plugin.

Sources and References

• Claude Code Plugin Documentation
• Language Server Protocol Specification
• Anthropic Demo Plugins Marketplace