The Best Claude Code Plugins in 2026: What 10 Million Installs Say (and the Ones Worth Keeping)

Two plugins own a quarter of Claude Code.

I run my whole company out of Claude Code. The product, the marketing site, the desktop app, the WhatsApp gateway, the blog you're reading. One founder, one terminal, a lot of plugins I installed on a Tuesday night and forgot about.

So before writing yet another "best plugins" list, I did the boring thing. I pulled the install stats Anthropic publishes for its official marketplace. 598 plugins. 10.2 million installs. And the shape of it surprised me.

The top 2 plugins hold 23.5% of every install. The median plugin has 236. And almost nothing in the top 25 touches the business you're building the code for.

That last part is the reason this post exists. Everybody is tooling up Claude to write code. Very few people are giving it the invoices, the clients or the hours. I think that's the bigger gap, and I'll show you the numbers.

The short answer: the best Claude Code plugins in 2026 are frontend-design for UI, Context7 for current library docs, Playwright so Claude can check its own work in a browser, and the GitHub MCP server for issues and PRs. Code review is now built into Claude Code, so check before you install a plugin for it. Keep the list short: 3 to 6 is plenty. And if you run a business, add one server that can see your money.

By the end of this article, you'll be able to:

• Tell a plugin, a skill, a hook and an MCP server apart, and know which one you actually need
• Read the real install data for all 598 plugins in the official marketplace
• Pick the coding plugins and MCP servers worth keeping, and the ones to skip
• Keep your setup fast and safe as the plugin count grows
• Copy a starter stack for your role, install commands included

What a Claude Code Plugin Actually Is

This is the part everyone gets confused by, me included. I once installed a "plugin", watched nothing happen, and spent twenty minutes convinced I'd broken my config. I hadn't. I just didn't know what I'd installed.

A plugin is a box. It holds up to four kinds of things, and you install them together with one command.

So "Context7 plugin" and "Context7 MCP server" are the same thing in a different wrapper. The plugin just saves you from writing the config yourself.

One more distinction worth knowing. Plugins are a Claude Code thing. MCP servers are portable: the same server URL works as a custom connector in Claude on the web, desktop and phone, in ChatGPT developer mode, and in Codex. If you want something you can use outside the terminal, you want the MCP server.

To install from the official marketplace, type /plugin in Claude Code to browse, or install by name:

/plugin install frontend-design@claude-plugins-official

598 Plugins, 10 Million Installs: What the Data Says

Anthropic publishes unique install counts for every plugin in its official marketplace, in the claude-plugins-official repo. The numbers below are all-time unique installs from the file generated on September 18, 2026.

Three things jump out.

• It's a power law. The top 10 plugins hold 53% of all installs. The top 25 hold 78%. 282 of the 598 plugins have 100 installs or fewer.
• The top 25 is entirely about writing software. UI, review, docs, browsers, git, deploys, language servers. Not one of them knows who your clients are.
• Installs are not usage. A lot of these were installed once, on day one, because a list like this one said so. Popular tells you what people tried. It doesn't tell you what they kept.

The Best Claude Code Plugins for Writing Code

For each one: what it does, where it breaks, and whether it earns a place. My bar is simple. If I'd notice it was gone within a week, it stays.

frontend-design

A single skill from Anthropic that pushes Claude away from the default look every AI app has: the purple gradient, the centered card, the Inter-on-white. It makes Claude pick a direction for type, color and layout before it writes a line.

Installs: 1.26M (#1 in the official marketplace). Install: /plugin install frontend-design@claude-plugins-official

Where it breaks. On an existing design system it can get "creative" when you wanted consistency. Tell it to follow your tokens and it behaves.

Verdict: Keep. I've had it installed since January. It's the one plugin I'd reinstall first on a new machine.

superpowers

A community skill library by Jesse Vincent. It teaches Claude a whole way of working: brainstorm first, write a plan, red/green TDD, hand pieces to subagents, review before merging.

Installs: 1.13M (#2 in the official marketplace). Install: /plugin install superpowers@claude-plugins-official

Where it breaks. It's opinionated by design. If you already have a process written into your CLAUDE.md, the two will argue. For a two-line fix, the ceremony is overkill.

Verdict: Situational. Great if you want a process handed to you. Skip it if you already have one.

code-review and code-simplifier

code-review runs several review agents over a PR and scores each finding by confidence, so the noise gets filtered out. code-simplifier cleans up the code you just changed without changing what it does.

Installs: 482K and 376K (#3 and #6 in the official marketplace). Install: /plugin install code-review@claude-plugins-official

Where it breaks. Recent versions of Claude Code ship /code-review and /simplify built in. Type / and check before you install duplicates.

Verdict: Keep the habit, check whether you need the plugin. I use the built-in commands on every diff that matters.

security-guidance

Hooks that warn on risky patterns as Claude edits, a diff review when it stops, and a commit reviewer that looks for injection, XSS, SSRF, hardcoded secrets and 25+ other classes of bug.

Installs: 267K (#12 in the official marketplace). Install: /plugin install security-guidance@claude-plugins-official

Where it breaks. Pattern warnings fire on false positives, and it adds a pass at the end of each turn. Claude Code also has a built-in /security-review for a one-off check of a branch.

Verdict: Keep if you ship anything that handles money or logins. That's most of us.

feature-dev

A guided workflow for bigger features: agents explore the codebase, propose an architecture, build it, then review it.

Installs: 274K (#10 in the official marketplace). Install: /plugin install feature-dev@claude-plugins-official

Where it breaks. Slow for small tasks. The value shows up on features that touch five files or more, where the exploration step stops Claude from inventing a pattern your codebase doesn't use.

Verdict: Situational. Use it for the big stuff, not the daily stuff.

skill-creator

Helps you write your own skills and test them against evals. Once you notice you've explained the same thing to Claude three times, this is how you stop.

Installs: 432K (#5 in the official marketplace). Install: /plugin install skill-creator@claude-plugins-official

Where it breaks. It's a tool for making tools. Useless until you have a repeated task worth capturing.

Verdict: Keep, once you're past week one.

Skip for now: ralph-loop (#15) runs Claude on the same task over and over until it's done. Fun, expensive, and rarely what you want on a real codebase. Output-style plugins change how Claude talks to you, which is taste, not capability.

The Best MCP Servers for Claude Code

Plugins change how Claude works. MCP servers change what it can reach. These are the ones that give Claude a system it genuinely can't get to on its own.

Context7

Claude's knowledge of a library freezes at its training date. Context7 fetches the docs for the exact version you use, from Upstash's hosted server, no local install. This is the fix for "Claude used an API that was renamed eight months ago." Keep.

Playwright

Microsoft's browser server lets Claude open your app, click through it and read what's on the page. The point isn't testing for its own sake. It's that Claude can check its own UI work before telling you it's done. "Types pass" and "the button works" are different claims. Keep.

GitHub

GitHub's official server. Read issues, open PRs, search code across repos. It exposes a lot of tools, so it's the heaviest server on this list. If you only need commits and PRs, the gh CLI already does most of it. Keep if you live in issues.

Your Stack's Own Server

Supabase, Vercel, Figma, Sentry, Linear. The rule is the same for all of them: install the server for the platform you already pay for, skip the rest. I run Vercel and Figma because that's where my app and my designs live. I don't run Linear because I don't use Linear. That sounds obvious. Look at your own list anyway.

Context and Memory Plugins

The other big category is Claude forgetting things. Every session starts from zero unless something carries the context forward.

• claude-md-management (#9, 316K). Audits your CLAUDE.md files and captures what you learned in a session. Useful, because a stale CLAUDE.md is worse than none.
• Serena (#25, 92K). Semantic code navigation over language servers, so Claude finds symbols instead of grepping. Worth it on big codebases, noise on small ones.
• remember (#32, 61K). A community plugin that compresses each conversation into daily logs so Claude knows what you did yesterday.

Before you install any of these, know that Claude Code now keeps its own memory files per project. Mine grew to 185 notes this year, and the index got so long that Claude Code started cutting lines off the end. That's the real lesson. Memory is only useful if it's short. More memory tooling won't fix a messy index.

The Business Gap: What Almost Nobody Installs

Here's the part none of the other lists cover.

I pulled every plugin in the marketplace that touches money, clients or operations. Payments, CRM, docs, project management. Here's how they rank.

Add up every business plugin I could find and you get about 1.7% of all installs. frontend-design alone has seven times more.

We gave Claude our codebase, our browser, our database and our deploys. Then we kept the invoices in a spreadsheet.

I get why. Claude Code started as a developer tool, and most of the people installing plugins are developers. But a lot of us are also the person sending the invoice. The freelancer, the solo founder, the two-person agency. For us, "what does Acme still owe me?" is a more expensive question than "why is this test flaky?"

Stripe

Stripe's plugin is built for developers wiring Stripe into an app. If you already bill through Stripe, its MCP server can also read your customers and invoices. Good if Stripe is your ledger. It doesn't know your hours, your contracts or who hasn't paid yet outside Stripe.

Notion

Notion's official server reads and writes your pages. If your client notes and SOPs live in Notion, this is how Claude finds them. It's a document store, so the numbers are only as good as the last time someone updated the page.

Accordio MCP

Disclosure: I built this one. Weigh it accordingly.

Accordio MCP is a remote MCP server for your freelance back office: tracked time, clients, projects, invoices, contracts, proposals, tasks, expenses and calendar. 44 tools behind one URL. It isn't in the official plugin marketplace yet, so you add it as an MCP server:

claude mcp add --transport http accordio https://mcp.accordio.ai/mcp

Then ask what you worked on today and Claude reads hours the free Mac tracker actually measured, not hours you remembered. Ask what's unbilled and it adds it up in money per client. Ask for the invoice and it drafts one from those hours. Nothing goes out until you confirm the exact recipient and amount. The same URL works as a custom connector in Claude on the web and on your phone.

Reading and tracking are free. Drafting invoices, proposals and contracts is the Legend plan, $39 a month. Setup for every host is at accordio.ai/mcp.

How Many Plugins Should You Run?

Three to six. Every serious list lands on roughly the same number, and there are two reasons.

Context. Every MCP server adds tool definitions Claude has to consider, and every skill adds a description it has to read. Recent Claude Code versions load MCP tool definitions on demand once you have a lot of them, so the cost is lower than it was in 2025. It isn't zero. A long list still means more wrong tools picked, more tokens spent deciding.

Trust. A hook is a shell command that runs on your machine, automatically, every time its event fires. An MCP server holds a token to your GitHub, your database or your bank data. Every plugin widens what you have to trust.

The marketplace has three rough levels of trust, and they're worth knowing:

None of that means community plugins are unsafe. superpowers is the #2 plugin for a reason. It means you should read what a hook does before you let it run on every edit. Five minutes on the repo is cheap.

A quick audit that works: type /plugin, look at what's installed, and remove anything you haven't noticed in two weeks. You won't miss it.

The Starter Stack for Your Role

If you want to skip the thinking, pick your row.

And whatever your row, use the built-in /code-review before you merge anything that matters.

Conclusion

The install data says Claude Code users want better UI, current docs and a second pair of eyes on their diffs. Fair. Those are the right first installs, and I run most of them.

But the data also shows what's missing. We built Claude a very good workshop and never showed it the books. If you bill clients, the most useful thing you can add this week isn't another coding plugin. It's one server that knows what you worked on and who owes you for it.

Browse plugins: /plugin in Claude Code · Install data: claude-plugins-official · Accordio MCP: accordio.ai/mcp