"Plugin" means different things in different places. In the Claude Code world, a plugin is a packaged bundle - it can ship MCP servers, skills, hooks, and config all at once, installable in a single command. If MCPs and skills are Lego bricks, a plugin is a pre-assembled Lego set. Useful exactly where the glue between pieces is what someone else already figured out.
A plugin is a coherent bundle of agent capabilities that travels together. You install it once and get everything at once. You uninstall it once and everything goes away cleanly.
Any combination of those pieces, shipped together as one unit. A plugin doesn't have to include all four layers - most ship just an MCP plus a skill or two. But the structure is there so complex bundles stay organized.
MCPs and skills on their own are great. But if you're building something real, you usually need several pieces working together: a tool, a prompt that knows how to use that tool, a hook that logs or sanitizes outputs, maybe some config. Building all of that yourself every time is tedious. Plugins let someone else bundle it once, and everyone else installs it.
Example: a "Telegram channel" plugin might ship:
Instead of you wiring those four things together, you type one command and get the whole thing working.
The mental model: MCPs and skills are the primitives; plugins are the products. Primitives give you building blocks. Products give you solutions. A well-designed plugin feels like "I installed the Telegram integration" instead of "I installed three separate things I need to configure together."
See Plugins vs MCP for a deeper comparison of when each is the right choice.
Most plugins live in marketplaces. Anthropic maintains the official marketplace with first-party plugins (Telegram, Slack, GitHub, Linear, Notion, etc.). A growing ecosystem of community plugins is on GitHub. See Marketplace for what exists and how to vet them.
Installing a plugin is one command inside Claude Code:
/plugin install telegram@claude-plugins-officialWhat happens: the plugin is downloaded. Its MCP servers get registered in your config. Its skills become invokable via slash commands. Its hooks get wired up to the right events. Its defaults apply. Uninstalling is one command and reverses all of that cleanly - no leftover config to clean up.
Beginner path: start with plugins from the official marketplace. Graduate to raw MCPs as you develop opinions about how you want things to work. Eventually, you might package your own plugins for patterns you've built - that's how the ecosystem grows.