# Official Claude Code Plugins: The Complete List (2026)

> The complete list of official Claude Code plugins from Anthropic in 2026 — first-party tools, 11 language servers, and integrations, with install commands.

Source: https://designrevision.com/blog/official-claude-code-plugins

---

Official Claude Code plugins are the ones Anthropic maintains and vets, published in the `claude-plugins-official` marketplace that Claude Code registers for you automatically. They are the safest place to start: first-party tools built by Anthropic plus a curated set of partner integrations, all installable with a single command. This is the complete list of Claude Code official plugins for 2026 — the first-party dev tools, the eleven language servers, the output styles, and the partner integrations — each with what it does and how to install it.

*Last updated: July 2026. The official marketplace grows constantly; run `/plugin` in a live session for the current catalog.*

## Key Takeaways

> If you remember nothing else:
>
> * **Official plugins** live in **`claude-plugins-official`**, maintained by Anthropic and **registered automatically** on first launch
> * There are two Anthropic marketplaces: **`claude-plugins-official`** (curated) and **`claude-community`** (reviewed third-party)
> * **First-party** plugins cover dev workflow (`code-review`, `security-guidance`), design (`frontend-design`), skill tooling (`skill-creator`), **11 language servers**, and output styles
> * **Partner integrations** (GitHub, Supabase, Vercel, Figma, Linear, Sentry, Notion, and more) ship as MCP plugins in the same marketplace
> * Install any with **`/plugin install <name>@claude-plugins-official`**
> * The marketplace holds **200+ plugins and grows** — run `/plugin` for the live list

## Table of Contents

1. [What Makes a Plugin "Official"?](#what-makes-a-plugin-official)
2. [Official First-Party Plugins](#official-first-party-plugins)
3. [Official Language-Server (LSP) Plugins](#official-language-server-lsp-plugins)
4. [Official Partner Integrations](#official-partner-integrations)
5. [How to Install Official Plugins](#how-to-install-official-plugins)
6. [Official vs. Community Plugins](#official-vs-community-plugins)
7. [Conclusion](#conclusion)

## What Makes a Plugin "Official"?

A plugin is "official" when it lives in **`claude-plugins-official`**, the marketplace Anthropic curates and maintains. In other words, Claude Code official plugins are the ones Anthropic stands behind — either built in-house or vetted before listing. Two things make this marketplace special: it is **registered automatically** the first time you launch Claude Code, so you can install from it with zero setup, and everything in it is either built by Anthropic or reviewed before it lands.

Within it, the Anthropic Claude Code plugins fall into two groups:

- **First-party plugins** — built and maintained by Anthropic itself (the dev-workflow tools, `frontend-design`, `skill-creator`, the language servers, and the output styles).
- **Partner integrations** — plugins for third-party tools (GitHub, Supabase, Figma, and dozens more) that Anthropic has reviewed and curated, most of them pre-configured MCP servers.

Anything outside this marketplace — the community marketplace, or an independent directory — is not "official," even if it is excellent. We cover that distinction at the end. For the wider picture of what plugins are, see our complete guide to [Claude Code plugins](/blog/claude-code-plugins).

## Official First-Party Plugins

These are the plugins Anthropic builds and maintains. All install with `/plugin install <name>@claude-plugins-official`.

### Dev workflow

- **`code-review`** — runs parallel agents over a change set to catch bugs, missed edge cases, and style issues before you commit. See our guide to [Claude Code for code review](/blog/claude-code-code-review).
- **`security-guidance`** — reviews Claude's diffs for injection, XSS, SSRF, exposed secrets, IDOR, and auth-bypass patterns. **Ships enabled by default** in recent Claude Code.
- **`commit-commands`** — helpers for crafting clean, conventional commits from your staged changes.
- **`pr-review-toolkit`** — a toolkit for reviewing pull requests, from summaries to line-level feedback.
- **`claude-code-setup`** — scans a repository (read-only) and recommends the hooks, skills, MCP servers, and subagents worth adding for that project. The fastest way to configure a fresh clone.
- **`plugin-dev`** — scaffolding and tooling for building and testing your own plugins.
- **`agent-sdk-dev`** — tooling for developing on the Claude Agent SDK.

### Design

- **`frontend-design`** — pushes Claude toward distinctive, production-grade UI instead of generic "AI slop." The highest-impact plugin for user-facing work; see our [Frontend Design plugin guide](/blog/claude-code-frontend-design-plugin).

### Skills tooling

- **`skill-creator`** — interviews you about a workflow and scaffolds a well-formed skill, and can evaluate and improve existing ones. The meta-plugin for extending Claude Code yourself.

### Output styles

- **`explanatory-output-style`** — layers educational explanations onto Claude's responses.
- **`learning-output-style`** — a learn-as-you-go mode that teaches while it works.

## Official Language-Server (LSP) Plugins

Language-server plugins give Claude real-time code intelligence — go-to-definition, find-references, and live type errors — instead of guessing from text. Anthropic ships eleven, one per language. Each requires the language's external server **binary** installed on your machine.

| Language | Plugin | Requires binary |
|----------|--------|-----------------|
| TypeScript | `typescript-lsp` | `typescript-language-server` |
| Python | `pyright-lsp` | `pyright-langserver` |
| Go | `gopls-lsp` | `gopls` |
| Rust | `rust-analyzer-lsp` | `rust-analyzer` |
| C / C++ | `clangd-lsp` | `clangd` |
| C# | `csharp-lsp` | `csharp-ls` |
| Java | `jdtls-lsp` | `jdtls` |
| Kotlin | `kotlin-lsp` | `kotlin-language-server` |
| Lua | `lua-lsp` | `lua-language-server` |
| PHP | `php-lsp` | `intelephense` |
| Swift | `swift-lsp` | `sourcekit-lsp` |

Install the one for your stack, e.g. `/plugin install typescript-lsp@claude-plugins-official`, then make sure the binary is on your `PATH`. Our [Claude Code LSP plugins guide](/blog/claude-code-lsp-plugins) covers setup end to end.

## Official Partner Integrations

Beyond its first-party tools, the official marketplace curates pre-configured **MCP plugins** — connections to external services over the Model Context Protocol — for the tools teams already use. Because Anthropic ships them pre-configured, you skip the manual server setup and just install with `/plugin install <name>@claude-plugins-official`:

| Category | Plugins |
|----------|---------|
| **Source control** | `github`, `gitlab` |
| **Infrastructure** | `supabase`, `firebase`, `vercel` |
| **Design** | `figma` |
| **Project management** | `linear`, `asana`, `atlassian` (Jira/Confluence), `notion` |
| **Monitoring** | `sentry` |
| **Communication** | `slack` |
| **Testing** | `playwright` |

This is a representative set, not the whole catalog — the official marketplace lists **200+ plugins and keeps growing**, so run `/plugin` to see everything available in your session. For the ones actually worth installing first, see our tested [best Claude Code plugins](/blog/best-claude-code-plugins) roundup.

## How to Install Official Plugins

Because `claude-plugins-official` is registered automatically, installing is a single command — no marketplace setup required:

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

Run `/plugin` on its own to open the interactive manager, where you can browse, enable, disable, and update any installed plugin, and `/reload-plugins` to apply changes without restarting. For the full step-by-step, see [how to install Claude Code plugins](/blog/how-to-install-claude-code-plugins).

## Official vs. Community Plugins

Anthropic runs **two** marketplaces, and knowing the difference keeps you safe:

| | `claude-plugins-official` | `claude-community` |
|---|---|---|
| **What's in it** | First-party + vetted partner plugins | Reviewed third-party plugins |
| **Registered** | Automatically, on first launch | Manually (`/plugin marketplace add anthropics/claude-plugins-community`) |
| **Install suffix** | `@claude-plugins-official` | `@claude-community` |
| **Trust level** | Highest — Anthropic-maintained | Reviewed, community-built |

Beyond both, independent directories index thousands of unofficial plugins from across the ecosystem — useful for discovery, but without Anthropic's review. When in doubt, start official. If you are still sorting out how plugins relate to skills, subagents, and MCP, our [skills vs. plugins vs. agents vs. MCP breakdown](/blog/claude-code-skills-vs-plugins-vs-agents) lays it out.

## Which Official Plugins to Install First

You do not need all 200. A sensible starter set of Claude Code official plugins:

1. **A language server for your stack** — `typescript-lsp`, `pyright-lsp`, or whichever matches your code — for real-time type intelligence.
2. **`code-review`** — a second pair of eyes on every change before you commit.
3. **`security-guidance`** — already on by default, so simply leave it enabled.
4. **`frontend-design`** — if you touch any UI at all.
5. **The integrations your team lives in** — `github` first, then `supabase`, `vercel`, `linear`, `sentry`, or `figma` as needed.

Add `skill-creator` and `plugin-dev` once you want to build your own capabilities. For honest keep-or-skip verdicts across the whole field — official and community — see our tested [best Claude Code plugins](/blog/best-claude-code-plugins) roundup.

## Conclusion

The official Claude Code plugins are the curated core of the ecosystem: Anthropic's own dev-workflow tools, `frontend-design`, `skill-creator`, eleven language servers, and two output styles, plus vetted partner integrations for GitHub, Supabase, Vercel, Figma, and dozens more — all in the auto-registered `claude-plugins-official` marketplace. Start here, install a language server and the integrations your team lives in, and layer community plugins on top once you know what you need.

From here, the tested [best Claude Code plugins](/blog/best-claude-code-plugins) roundup shows which to install first, and the complete [Claude Code plugins guide](/blog/claude-code-plugins) covers how the whole system fits together.

---

## Related Resources

- [Claude Code Plugins: The Complete Guide](/blog/claude-code-plugins)
- [Best Claude Code Plugins (2026): Tested & Ranked](/blog/best-claude-code-plugins)
- [How to Install Claude Code Plugins](/blog/how-to-install-claude-code-plugins)
- [Claude Code LSP Plugins: TypeScript Language-Server Setup](/blog/claude-code-lsp-plugins)
- [Claude Code Skills vs. Plugins vs. Agents vs. MCP](/blog/claude-code-skills-vs-plugins-vs-agents)