Plugins & Ecosystem

Imagine you've spent weeks developing the perfect Claude Code workflow: custom agents for code reviews, hooks for automatic linting checks, MCP servers for your database, skills for recurring tasks. Now a new team member joins -- and you have to explain everything individually and copy files one by one.

Plugins solve exactly this problem. A plugin bundles everything -- skills, agents, MCP configuration, and hooks -- into a single, portable package. You install it with one command, and the entire toolkit is immediately available.

Plugins as an App Store for Claude Code

Think of plugins like apps on your smartphone. Each app brings its own functionality without interfering with other apps. Claude Code plugins work the same way:

One plugin = one complete toolkit: A security plugin might contain a security review agent, a vulnerability scanner as an MCP server, a pre-commit hook for secrets detection, and skills for OWASP checks -- all in one package.
Installation with one command: No manual file copying. One /plugin command, and everything runs.
Independent of each other: Plugins don't affect each other because each plugin has its own namespace.

iNamespace Isolation

Every skill in a plugin automatically gets a prefix: /plugin-name:skill-name. If two plugins each have a skill named review, there's no conflict -- they're called /security-plugin:review and /perf-plugin:review. The same principle as packages in a programming language.

What a Plugin Can Contain

A plugin has a modular structure. Not every component is required -- you can also create a plugin that only contains skills:

Skills -- Reusable prompt templates and workflows
Agents -- Specialized subagents with their own system prompt and model
Hooks -- Event handlers for automatic actions (PreToolUse, PostToolUse, etc.)
MCP Servers -- Tool integrations for external services
Settings -- Configuration for model, permissions, and behavior

What to Expect

Plugin Structure -- How a plugin is built, from the manifest to namespace isolation
MCP Integration -- Claude Code as an MCP host with transport types, deferred loading, and configuration scopes
Marketplace & Community -- Where to find, share, and manage plugins for enterprise environments

*Learning Objective

After this module, you'll be able to create and distribute your own plugins, efficiently configure MCP servers, and leverage the growing ecosystem around Claude Code for your workflows.

Reflect

Plugins transform individual workflows into shareable team toolkits. Combined with the MCP protocol and an active community, an ecosystem emerges that extends Claude Code far beyond its built-in features. In the next section, we'll look at how a plugin is concretely structured.