Fundamentals

What Are Claude Code Plugins?

Plugins are shareable packages that bundle commands, agents, hooks, and MCP servers into single installable units.

The Problem Plugins Solve

Before plugins, setting up Claude Code with custom commands, agents, and integrations meant scattered configuration files across different projects. When teammates asked "How do I set up the same thing?", reproducing your setup was tedious and error-prone.

Plugin Components

Plugins can include any combination of these four component types:

Commands

Slash commands that provide shortcuts for common tasks

Commands are custom shortcuts you can invoke with a forward slash (/) in Claude Code. They execute predefined workflows, from simple text expansions to complex automation scripts.

Example: /deploy - Deploy your application to production

Agents

Specialized AI agents that handle specific tasks

Subagents are Claude instances configured with specific expertise. They can handle specialized tasks like code review, testing, or database management with domain-specific knowledge.

Example: security-reviewer - Specialized agent for security audits

Hooks

Event-triggered workflows at specific lifecycle points

Hooks let plugins run custom scripts automatically at specific points in your workflow - before commits, after saves, or during other Claude Code operations.

Example: pre-commit hook - Run tests before every commit

MCP Servers

Connections to external tools and data sources

Model Context Protocol (MCP) servers provide standardized connections to external services like databases, APIs, cloud providers, and development tools.

Example: GitHub MCP - Access repositories and pull requests

Plugins vs. Individual Components

Individual Components

Single commands, agents, or MCP servers configured manually

  • One component at a time
  • Manual configuration required
  • Harder to share with others
Plugins

Bundled collections that work together seamlessly

  • Multiple components in one package
  • One-command installation
  • Easy to share and standardize

Real-World Example

Imagine you're working on a web application that needs deployment automation. A DevOps plugin might include:

/deploy command

One-command secure deployments

Infrastructure agent

Specialized knowledge of your cloud setup

Cloud provider MCP

Direct connections to AWS/Vercel/etc.

Pre-deployment hook

Run security scans before every deployment

Next Steps

Now that you understand what plugins are, learn how to install and use them.