Best Claude Code Plugins in 2026 (Ranked)

Updated June 2026

The best Claude Code plugins in 2026 are the official marketplace plugins that close a real workflow gap: a language LSP plugin for code intelligence, GitHub for repository and pull request context, Security Guidance and Semgrep for safer edits, Context7 for current documentation, and Frontend Design for UI work. If you install only one, start with the LSP plugin for your primary language. It gives Claude Code IDE-grade navigation and type awareness, and it takes one command to set up. Everything else is additive once that foundation is in place.

A plugin in Claude Code is a bundle. A single install can add slash commands, subagents, hooks, and MCP server connections in one step, which is why plugins replaced the old practice of wiring each of those pieces by hand. Anthropic launched the official plugin marketplace in late 2025, and by mid 2026 it carries more than 30 official plugins plus hundreds of community ones.

Quick comparison table

Plugin	What it does	Best for	Our pick
Language LSP (TypeScript, Pyright, Go, Rust, etc.)	Adds IDE-grade code intelligence and navigation for your language	Every project, regardless of stack	Start here
GitHub	Repository, issue, and pull request context inside the session	Repo and PR work being the bottleneck	#2 priority
Security Guidance	Real-time warnings about unsafe code patterns while editing	Auth, payments, or user-data code	Add early, low cost
Semgrep	Rule-driven static analysis and security scanning	Catching vulnerabilities before merge	Pairs with Security Guidance
Context7	Live, version-specific documentation lookup during generation	Stale library docs slowing you down	High value, 340K-plus installs
Frontend Design	Production-grade UI design and visual quality passes	Frontend and design-heavy work	Among the most-installed
PR Review Toolkit	Structured pull request analysis across tests and quality	Teams running real PR review	Best for teams
Commit Commands	Git commit, push, and PR creation workflows	Cleaning up your git ergonomics	Quiet daily time-saver
Superpowers	Skills for brainstorming, TDD, and structured debugging	Workflow depth beyond stock prompts	Popular, 750K-plus installs
Playwright	Browser automation and end-to-end test execution	Frontend QA and bug reproduction	Add when you ship UI

The ten best Claude Code plugins

1. Language LSP plugin (start here)

The single highest-value plugin for any project is the Language Server Protocol plugin for your primary language. The official marketplace ships typescript-lsp, pyright-lsp (Python), gopls-lsp (Go), rust-analyzer-lsp, and equivalents for Java, PHP, C/C++, Kotlin, Swift, and Lua. Each one gives Claude Code the same code intelligence your IDE has: go-to-definition, type checking, symbol search, and accurate diagnostics.

This matters because without an LSP, Claude Code reasons about your code as text. With one, it reasons about your code as a typed graph. The difference shows up immediately in how often it picks the right function signature and how rarely it hallucinates an API that does not exist. Install it with /plugin install typescript-lsp@claude-plugins-official (swap in the plugin for your language).

2. GitHub

The GitHub plugin connects Claude Code to your repositories, issues, and pull requests. Instead of pasting diffs and issue text into the session, you let the agent read PR context, comment on reviews, and open pull requests directly. For most developers, repository and PR work is the biggest external workflow gap, which makes this the natural second install after a language LSP. Install with /plugin install github@claude-plugins-official.

3. Security Guidance

Security Guidance is a lightweight official plugin that warns you in real time when Claude Code is about to write an unsafe pattern: a hardcoded secret, an unsanitized query, an insecure default. It is cheap to run and adds a safety net precisely where it matters most, on code that touches authentication, payments, or user data. There is little reason not to add it early. Install with /plugin install security-guidance@claude-plugins-official.

4. Semgrep

Where Security Guidance gives inline nudges, Semgrep runs rule-driven static analysis across your codebase and reports findings against a large library of security rules. It is the heavier, more thorough security layer, and it pairs naturally with Security Guidance: one catches issues as you type, the other audits the whole tree before you merge. Install with /plugin install semgrep@claude-plugins-official.

5. Context7

Context7 solves the stale-documentation problem. When Claude Code generates code against a library, Context7 fetches the current, version-specific docs and examples so the output matches the API that actually ships today rather than the one from the model's training cutoff. With more than 340,000 installs it is one of the most-used plugins in the marketplace, and on any project that pulls in fast-moving dependencies it pays for itself the first time it stops a deprecated-method bug. Install with /plugin install context7@claude-plugins-official.

6. Frontend Design

Frontend Design is among the most-installed plugins in the official marketplace. It pushes Claude Code toward production-grade UI: better visual hierarchy, accessible defaults, and design quality passes that go beyond "make it work." If your work is frontend-heavy, this is the plugin that most changes the quality of what the agent produces. Install with /plugin install frontend-design@claude-plugins-official.

7. PR Review Toolkit

The PR Review Toolkit runs comprehensive pull request analysis: it checks tests, surfaces quality regressions, and produces structured review feedback across a whole changeset rather than a single file. For teams that run real pull request review, it is the most complete of the official review plugins. Solo developers may prefer the lighter code-review plugin, which gives structured AI review without the full toolkit. Install with /plugin install pr-review-toolkit@claude-plugins-official.

8. Commit Commands

Commit Commands is a small plugin that quietly improves your git ergonomics every day. It adds clean workflows for staging, committing with well-formed messages, pushing, and opening pull requests, all from inside the session. It is not glamorous, but it removes a dozen small context switches a day. Install with /plugin install commit-commands@claude-plugins-official.

9. Superpowers

Superpowers is a skills-focused plugin with more than 750,000 installs. It adds structured workflows for brainstorming, test-driven development, and systematic debugging, giving Claude Code a deeper repertoire than stock prompting. It is the plugin to reach for when you want the agent to follow a disciplined process rather than improvise. Install with /plugin install superpowers@claude-plugins-official.

10. Playwright

The Playwright plugin gives Claude Code browser automation and end-to-end testing. It can drive a real browser to reproduce a bug, run a UI flow, or execute an end-to-end suite and read the results. Add it when you start shipping user interface work and need the agent to verify behavior in a browser rather than reason about it abstractly. Install with /plugin install playwright@claude-plugins-official.

How to install a Claude Code plugin

Plugins come from marketplaces. The official marketplace, claude-plugins-official, is available by default, so installing an official plugin is a single command:

/plugin install github@claude-plugins-official

The pattern is always /plugin install <name>@<marketplace>. Installed plugins live in ~/.claude/plugins/ and work across every project once installed globally. You can browse the full official catalog at claude.com/plugins, and refresh it with /plugin marketplace update claude-plugins-official.

To add a community marketplace, point Claude Code at its repository:

/plugin marketplace add ComposioHQ/awesome-claude-plugins

After adding a marketplace you install from it the same way, using that marketplace's name after the @. Community marketplaces are where you find plugins the official catalog does not carry, but treat them with the same caution you would any third-party code: a plugin can add hooks and MCP servers that run with your permissions, so install from sources you trust.

How many plugins should you run?

Fewer than the catalog tempts you to. The honest recommendation, echoed by most developers who have tested the marketplace at length, is to start with three or four plugins that each close a concrete gap, run them for a couple of weeks, and only add more when you hit a workflow they would have solved.

A sensible starting stack:

1. Your language LSP plugin (code intelligence)
2. GitHub (repository and PR context)
3. Security Guidance or Semgrep (safer edits)
4. Context7 (current documentation)

Add Frontend Design if you work on UI, Playwright when you need browser verification, and a review plugin when your team formalizes pull request review. The reason to stay lean is the same reason it applies to MCP servers: every plugin that adds tools consumes part of the agent's attention budget, and a bloated tool surface makes the agent slower and less precise, not more capable.

A pre-wired alternative: the whole stack as an OS

Plugins are à la carte. You pick each one, install it, and tune how they interact. That works well once you know what you want, but it leaves you assembling and maintaining the stack yourself.

Claudify takes the other approach: it ships a complete operating system for Claude Code, with 1,700-plus skills, nine specialist agents, hooks, and a pre-configured MCP layer already calibrated to work together. Where installing ten plugins means ten separate decisions about tools and scope, an OS arrives wired: the skills, agents, and integrations are designed as one system rather than ten that happen to coexist. If you want the curated stack in a single install instead of building it plugin by plugin, that is the trade Claudify makes. For the underlying mechanics of how plugins, skills, and agents fit together, see our Claude Code plugins explainer and the Claude Code setup guide.

Frequently asked questions

How do I install a Claude Code plugin?

Use the /plugin install command with the plugin name and its marketplace, for example /plugin install github@claude-plugins-official. The official marketplace is available by default, so official plugins install in one step. To use a community plugin, first add its marketplace with /plugin marketplace add owner/repo, then install from it the same way. Installed plugins live in ~/.claude/plugins/ and work across all your projects. See the Claude Code plugins explainer for the full plugin anatomy.

Are Claude Code plugins free?

The official Anthropic plugins are free, open, and maintained by Anthropic. You still pay for Claude Code usage itself through your subscription or API key, but the plugins add no separate charge. Some plugins connect to third-party services (Sentry, Linear, Vercel) that have their own pricing, and a few community plugins wrap paid tools, but the official marketplace plugins themselves cost nothing to install.

What is the difference between a Claude Code plugin and an MCP server?

An MCP server is one type of integration: it connects Claude Code to an external tool or service such as a database, GitHub, or a browser. A plugin is a broader bundle that can include an MCP server connection alongside slash commands, subagents, and hooks, all installed in one step. In other words, many plugins ship an MCP server inside them, but a plugin can also add commands and agents that an MCP server alone cannot. If you want the integrations on their own, see our guide to the best MCP servers for Claude Code.

---

Get Claudify. A complete Claude Code OS with 1,700-plus skills, nine specialist agents, and the MCP layer pre-wired, installed in one command.