Extend Claude Code.
Automate Everything.
Claude Code is more than a coding assistant. With hooks, skills, plugins, and MCP servers, you can make it do exactly what you need — automatically, repeatably, and shareable with your team.
Hooks auto-format code after every edit and run tests before Claude stops. Zero manual effort.
Why Extend Claude Code?
Out of the box, Claude Code is powerful. But the real magic happens when you customize it for your workflow. Here's what extensions unlock:
Automate the Repetitive
Format code, run linters, validate schemas, reload configs — all triggered automatically, no manual steps.
Codify Your Workflows
Turn your team's best practices into slash commands. /deploy, /review, /research — type it and it happens.
Share & Reuse
Package your extensions into plugins. Install community plugins with one command. Build on what others have built.
Connect Everything
MCP servers bridge Claude to GitHub, Jira, Slack, databases, and any API — making it the hub of your dev stack.
The Four Layers of Extensibility
Claude Code's extension system is layered. Each layer builds on the previous, from simple automation to full ecosystem integration.
Hooks
Shell commands that fire automatically on lifecycle events. Deterministic, reliable, zero effort.
Skills
Custom slash commands powered by markdown. Reusable instructions, templates, and workflows.
Plugins
Shareable packages that bundle skills, hooks, MCP servers, and agents into one installable unit.
MCP Servers
External tool connections via the open Model Context Protocol. GitHub, Slack, databases, and beyond.
Most people get the biggest productivity boost from a few well-chosen hooks. They're the simplest to set up and the most immediately rewarding. You can always add skills, plugins, and MCP servers later.
When to Use What
| I want to... | Use | Example |
|---|---|---|
| Auto-run something after edits | Hook | Format code with Prettier after every file change |
| Block dangerous commands | Hook | Prevent rm -rf or edits to .env |
| Create a reusable workflow | Skill | /deploy staging runs your deploy checklist |
| Run something repeatedly | Skill (/loop) |
Check deploy status every 5 minutes |
| Share workflows with my team | Plugin | Bundle company-wide skills into an installable package |
| Query an external API | MCP Server | Search GitHub issues or read Jira tickets from Claude |
| Remember across sessions | Community tool | Severance or Claude-Mem for semantic memory |
What Does It Cost?
One of the first questions I had: do I need more subscriptions? Here's the honest breakdown.
| Layer | Cost | Details |
|---|---|---|
| Claude Code | Paid | Requires Claude Pro ($20/mo), Team ($25/user/mo), or Enterprise plan. Or API usage via Max plan ($100-200/mo). |
| Hooks | Included | Built into Claude Code. No extra cost. Runs your existing shell commands. |
| Skills | Included | Built into Claude Code. Markdown files — nothing to install or pay for. |
| Plugins | Free | Community plugins are free. Installing them is free. Creating them is free. |
| MCP Servers | Varies | The protocol is free. Individual servers may need API keys (GitHub free, Slack free tier, some DBs need hosting). |
| Severance | Free | Open source. Uses your existing Claude Code session — no extra API calls. |
| Claude-Mem | Free | Open source plugin. Runs locally, no external services needed. |
The only additional costs come from specific MCP servers that need third-party API keys (like a paid Slack workspace or hosted database). Most developers already have these.
Explore the Guide
Hooks
Automatic actions on lifecycle events. Auto-format, block edits, send notifications, and more.
Skills
Custom slash commands. Build reusable workflows your whole team can invoke.
Plugins
Shareable packages. Bundle skills, hooks, and servers into one installable unit.
MCP Servers
Connect Claude to external tools — GitHub, databases, Slack, and any API.
Community
Severance, awesome-claude-code, and the growing ecosystem of community projects.
Get Started
Set up your first hook, skill, and MCP server in under 5 minutes.
If you find it useful, the best way to support it is to share it with other developers. If you spot an error or want to suggest an addition, I'd love to hear from you.