What it does
Claude Code plugins extend the editor with new capabilities—everything from Git integrations to Docker management, database clients, and AI tools. The plugin marketplace is where you discover and install them. When you run /plugin marketplace add, you're browsing the built-in plugin registry, filtering by category (version control, containerization, language tools), searching by name, and installing with a single command. Installation downloads the plugin bundle, registers it in your local configuration, and makes it immediately available in the terminal via /plugin <name> commands or through the UI.
Each plugin is a self-contained package with a manifest (metadata, required environment), bundled tools (MCP servers or Claude Code integrations), and optional hooks that run on events like "when a file saves" or "before you run tests." Scopes define what the plugin can access—filesystem read/write, network, environment variables—so you understand the security model before installing.
When to use it
Start with /plugin marketplace add when you notice yourself manually running the same CLI commands over and over. For example, if you're constantly checking Docker container status, building images, or managing networks, a Docker plugin saves you typing and gives you structured output. If your workflow involves Postgres, a database plugin lets you query tables, inspect schema, and run migrations from within Claude Code instead of switching to psql.
Plugins shine in three scenarios: language-specific tooling (Node.js, Python, Rust tools that aren't worth building yourself), infrastructure as code (Terraform, Kubernetes, CloudFormation helpers), and workflow glue (Slack notifications, GitHub checks, linear ticket creation). Use them to automate the boring parts of your development loop.
Try it yourself
Open the terminal and explore the marketplace without committing to anything—search for a tool relevant to your current project (Docker, database, Git workflow), read the manifest, and scan the scopes it requests. Once you find one that matches your needs, install it and try the first command. The plugin's help output (/plugin <name> help) will show you what commands are available.
Gotchas
Scope creep: A plugin requesting read/write access to your entire home directory is a red flag. Trust the scopes—they're enforced at the OS level. Review them before installation, especially for third-party plugins.
Version lock-in: Some plugins depend on specific tool versions (Docker 20.10+, Node.js 18+). If the plugin fails with a cryptic error, check the manifest's requires field and verify your environment matches.
Inactive plugins: A plugin listed in the marketplace doesn't mean it's maintained. Check the bundle's changelog and install date—if it hasn't been updated in six months and you're on a newer OS, it might break. Uninstall it with /plugin remove <name> if it stops working.
Conflicting CLI names: If a plugin exports a command that shadows your shell's built-in (e.g., a custom test command when you have Jest tests), the plugin takes precedence in Claude Code. Rename or disable the plugin binding if it interferes.
Try it yourself
Type the command in the fake terminal. Nothing leaves your browser.