What a Claude Code plugin actually is
A Claude Code plugin is one install that bundles several capabilities together for a specific job. Instead of adding a slash command here, a subagent there, and an MCP server somewhere else, a plugin packages them as a unit you turn on once. The agent then shows up already knowing how to do that job.
Think of it as a kit. A code-review plugin might ship the review command, a reviewer subagent, the hooks that run it automatically, and the connection to your repo - all in one. You install the kit, not the individual parts.
What can live inside a Claude Code plugin
| Piece | What it adds |
|---|---|
| Slash commands | Shortcuts that trigger a packaged workflow |
| Subagents | Specialist workers for one kind of task |
| MCP servers | Connections to your tools and data |
| Hooks | Actions that fire automatically on events |
| Skills | Packaged know-how the agent applies |
How plugins differ from skills and MCP servers
Plugins, skills, and MCP servers are easy to confuse because a plugin can contain the other two. The simplest way to hold it: a skill is know-how, an MCP server is a connection, and a plugin is the box that ships them together for a job.
- A skill teaches the agent how to do something - a repeatable method it follows.
- An MCP server connects the agent to an outside tool or data source so it can act on real systems.
- A plugin bundles commands, subagents, skills, MCP servers, and hooks into one install aimed at a single job.
So you do not choose between them - plugins are how the others travel together. If you want the deeper breakdown of each part on its own, read [skills, subagents, MCP, and hooks: when to use each](/blog/claude-code-skills-subagents-mcp-hooks-when-to-use), and for connections specifically, [the best Claude Code MCP servers to install](/blog/best-claude-code-mcp-servers).
The best Claude Code plugins to install, by job
The best Claude Code plugins are not the flashiest - they are the ones that match a job you already do over and over. Install by job, not by hype. These are the categories worth a plugin for most builders, and what each one unlocks.
- Code review: a plugin that adds a review command plus a reviewer subagent, so every change gets a second pair of eyes before it ships.
- Testing and QA: bundles a test-runner workflow and hooks that run your suite automatically, so the agent verifies its own work inside the loop.
- Git and pull requests: packages commit, branch, and PR commands so the agent can open clean, well-described pull requests for you.
- Documentation: a plugin that keeps READMEs, changelogs, and inline docs current as the code changes, instead of letting them rot.
- Project memory and context: connects the agent to your project's standards and history so it stops re-asking what it should already know.
- Security review: adds a pass that flags risky patterns - exposed keys, unsafe inputs, missing auth - before they reach production.
- Frontend and design: bundles the commands and context for building UI to a consistent style instead of a different look every time.
How to install a plugin in Claude Code
Installing a plugin is a short, repeatable flow. The point is that one install brings in everything the plugin bundles - commands, subagents, connections, and hooks - so you are configured for the job in a single step.
- Open Claude Code in the desktop app, IDE, web, or terminal - plugins work the same across all of them.
- Browse the plugin you want and confirm what it bundles, so you know which commands and connections you are adding.
- Install it, then approve any permissions or connections it needs, like access to your repo or a tool.
- Run the plugin's main command on a real task to confirm it behaves the way you expect.
- Keep it only if it earns its place. If you never reach for it, remove it.
If this is early in your setup, install plugins after you have your first few skills in place. Our guide to [the Claude Code skills to install first](/blog/claude-code-skills-to-install-first) is the right starting point, and plugins build on top of that foundation.
How to choose plugins without bloating your setup
More plugins is not better. Every plugin you add is more for the agent to consider and more for you to maintain. The CCC rule is simple: a plugin earns its place by saving you real time on a job you actually do, or it comes back out.
- Install for a job you do weekly, not one you might do someday.
- Add one at a time and use it on a real task before adding the next.
- Prefer a plugin that bundles a complete workflow over one that adds a single loose command.
- Review your installed plugins now and then, and remove anything you have not reached for.
- If two plugins overlap, keep the one you actually use and drop the other.
Frequently asked questions
What is a Claude Code plugin?
A Claude Code plugin is a single install that bundles slash commands, subagents, MCP servers, hooks, and skills for one job. Instead of wiring those pieces up separately, you install the plugin once and the agent shows up ready to do that job.
What is the difference between a plugin and an MCP server?
An MCP server is a connection that lets the agent act on an outside tool or data source. A plugin is a larger bundle that can contain MCP servers along with commands, subagents, and hooks. The plugin is the box; the MCP server is one thing inside it.
Which Claude Code plugins should I install first?
Start with the job that costs you the most time, usually code review or testing. Those are the steps builders skip when moving fast, and a plugin makes them automatic. Add one plugin at a time and only keep the ones you actually use.
Do plugins work outside the terminal?
Yes. Plugins work the same whether you run Claude Code in the desktop app, an IDE, the web, or the terminal. The install and the bundled commands behave consistently across all of them.
Can too many plugins slow Claude Code down?
Yes, in the sense that every plugin is more for the agent to weigh and more for you to maintain. Keep your setup lean: install for jobs you do regularly, add one at a time, and remove plugins you stop reaching for.
Are plugins the same as skills?
No. A skill is packaged know-how the agent follows. A plugin is a bundle that can include skills along with commands, subagents, MCP servers, and hooks. Skills can ship on their own or as part of a plugin.
Last reviewed by Duncan Rogoff on June 23, 2026
