Plugins

Extend Claude Code with custom commands, agents, hooks, Skills, and MCP servers through the plugin system.

Plugins let you extend Claude Code with custom functionality that can be shared across projects and teams. Install plugins from marketplaces to add pre-built commands, agents, hooks, Skills, and MCP servers, or create your own to automate your workflows.

Quickstart

Let's create a simple greeting plugin to get you familiar with the plugin system. We'll build a working plugin that adds a custom command, test it locally, and understand the core concepts.

Prerequisites

• Claude Code installed on your machine
• Basic familiarity with command-line tools

Create your first plugin

mkdir test-marketplace
cd test-marketplace

mkdir my-first-plugin
cd my-first-plugin

mkdir .claude-plugin
cat > .claude-plugin/plugin.json << 'EOF'
{
"name": "my-first-plugin",
"description": "A simple greeting plugin to learn the basics",
"version": "1.0.0",
"author": {
"name": "Your Name"
}
}
EOF

mkdir commands
cat > commands/hello.md << 'EOF'
---
description: Greet the user with a personalized message
---

# Hello Command

Greet the user warmly and ask how you can help them today. Make the greeting personal and encouraging.
EOF

cd ..
mkdir .claude-plugin
cat > .claude-plugin/marketplace.json << 'EOF'
{
"name": "test-marketplace",
"owner": {
"name": "Test User"
},
"plugins": [
{
"name": "my-first-plugin",
"source": "./my-first-plugin",
"description": "My first test plugin"
}
]
}
EOF

cd ..
claude

/plugin marketplace add ./test-marketplace

/plugin install my-first-plugin@test-marketplace

/hello

You've successfully created and tested a plugin with these key components:

• Plugin manifest (.claude-plugin/plugin.json) - Describes your plugin's metadata
• Commands directory (commands/) - Contains your custom slash commands
• Test marketplace - Allows you to test your plugin locally

Plugin structure overview

Your plugin follows this basic structure:

my-first-plugin/
├── .claude-plugin/
│   └── plugin.json          # Plugin metadata
├── commands/                 # Custom slash commands (optional)
│   └── hello.md
├── agents/                   # Custom agents (optional)
│   └── helper.md
├── skills/                   # Agent Skills (optional)
│   └── my-skill/
│       └── SKILL.md
└── hooks/                    # Event handlers (optional)
    └── hooks.json

Additional components you can add:

• Commands: Create markdown files in commands/ directory
• Agents: Create agent definitions in agents/ directory
• Skills: Create SKILL.md files in skills/ directory
• Hooks: Create hooks/hooks.json for event handling
• MCP servers: Create .mcp.json for external tool integration

Install and manage plugins

Learn how to discover, install, and manage plugins to extend your Claude Code capabilities.

Prerequisites

• Claude Code installed and running
• Basic familiarity with command-line interfaces

Add marketplaces

Marketplaces are catalogs of available plugins. Add them to discover and install plugins:

/plugin marketplace add your-org/claude-plugins

/plugin

For detailed marketplace management including Git repositories, local development, and team distribution, see Plugin marketplaces.

Install plugins

Via interactive menu (recommended for discovery)

/plugin

Select "Browse Plugins" to see available options with descriptions, features, and installation options.

Via direct commands (for quick installation)

/plugin install formatter@your-org

/plugin enable plugin-name@marketplace-name

/plugin disable plugin-name@marketplace-name

/plugin uninstall plugin-name@marketplace-name

Installation scopes

Plugins can be installed at different scopes to control their availability and sharing:

When to use each scope:

• User scope (default): For plugins you want available in all your projects
• Project scope: For plugins your team should share (committed to git)
• Local scope: For personal plugins in a specific project (not shared)

claude plugin install formatter@your-org

claude plugin install formatter@your-org --scope project

claude plugin install formatter@your-org --scope local

The --scope option also works with uninstall, enable, and disable commands:

claude plugin uninstall formatter@your-org --scope project

Verify installation

After installing a plugin:

1. Check available commands: Run /help to see new commands
2. Test plugin features: Try the plugin's commands and features
3. Review plugin details: Use /plugin → "Manage Plugins" to see what the plugin provides

Set up team plugin workflows

Configure plugins at the repository level to ensure consistent tooling across your team. When team members trust your repository folder, Claude Code automatically installs specified marketplaces and plugins.

To set up team plugins:

1. Add marketplace and plugin configuration to your repository's .claude/settings.json
2. Team members trust the repository folder
3. Plugins install automatically for all team members

For complete instructions including configuration examples, marketplace setup, and rollout best practices, see Configure team marketplaces.

Develop more complex plugins

Once you're comfortable with basic plugins, you can create more sophisticated extensions.

Add Skills to your plugin

Plugins can include Agent Skills to extend Claude's capabilities. Skills are model-invoked—Claude autonomously uses them based on the task context.

To add Skills to your plugin, create a skills/ directory at your plugin root and add Skill folders with SKILL.md files. Plugin Skills are automatically available when the plugin is installed.

For complete Skill authoring guidance, see Agent Skills.

Organize complex plugins

For plugins with many components, organize your directory structure by functionality. For complete directory layouts and organization patterns, see Plugin directory structure.

Test your plugins locally

When developing plugins, use a local marketplace to test changes iteratively. This workflow builds on the quickstart pattern and works for plugins of any complexity.

mkdir dev-marketplace
cd dev-marketplace
mkdir my-plugin

dev-marketplace/
├── .claude-plugin/marketplace.json  (you'll create this)
└── my-plugin/                        (your plugin under development)
├── .claude-plugin/plugin.json
├── commands/
├── agents/
└── hooks/

mkdir .claude-plugin
cat > .claude-plugin/marketplace.json << 'EOF'
{
"name": "dev-marketplace",
"owner": {
"name": "Developer"
},
"plugins": [
{
"name": "my-plugin",
"source": "./my-plugin",
"description": "Plugin under development"
}
]
}
EOF

cd ..
claude

/plugin marketplace add ./dev-marketplace

/plugin install my-plugin@dev-marketplace

/plugin uninstall my-plugin@dev-marketplace

/plugin install my-plugin@dev-marketplace

Debug plugin issues

If your plugin isn't working as expected:

1. Check the structure: Ensure your directories are at the plugin root, not inside .claude-plugin/
2. Test components individually: Check each command, agent, and hook separately
3. Use validation and debugging tools: See Debugging and development tools for CLI commands and troubleshooting techniques

Share your plugins

When your plugin is ready to share:

1. Add documentation: Include a README.md with installation and usage instructions
2. Version your plugin: Use semantic versioning in your plugin.json
3. Create or use a marketplace: Distribute through plugin marketplaces for installation
4. Test with others: Have team members test the plugin before wider distribution

Next steps

Now that you understand Claude Code's plugin system, here are suggested paths for different goals:

For plugin users

• Discover plugins: Browse community marketplaces for useful tools
• Team adoption: Set up repository-level plugins for your projects
• Marketplace management: Learn to manage multiple plugin sources
• Advanced usage: Explore plugin combinations and workflows

For plugin developers

• Create your first marketplace: Plugin marketplaces guide
• Advanced components: Dive deeper into specific plugin components:
  • Slash commands - Command development details
  • Subagents - Agent configuration and capabilities
  • Agent Skills - Extend Claude's capabilities
  • Hooks - Event handling and automation
  • MCP - External tool integration
• Distribution strategies: Package and share your plugins effectively
• Community contribution: Consider contributing to community plugin collections

For team leads and administrators

• Repository configuration: Set up automatic plugin installation for team projects
• Plugin governance: Establish guidelines for plugin approval and security review
• Marketplace maintenance: Create and maintain organization-specific plugin catalogs
• Training and documentation: Help team members adopt plugin workflows effectively

See also

• Plugin marketplaces - Creating and managing plugin catalogs
• Slash commands - Understanding custom commands
• Subagents - Creating and using specialized agents
• Agent Skills - Extend Claude's capabilities
• Hooks - Automating workflows with event handlers
• MCP - Connecting to external tools and services
• Settings - Configuration options for plugins

To find navigation and other pages in this documentation, fetch the llms.txt file at: https://code.claude.com/docs/llms.txt