Best Claude Code Plugins in 2026: Official, MCP, LSP, Design, and Workflow Picks

've been using Claude Code, and there hasn't been a day I haven't used a plugin. It genuinely makes everything so convenient. Instead of rebuilding the same setup with custom commands, MCP configs, hooks, and project notes, plugins let you package those workflows and install them as needed.

If you want it to design pages instead of repeat prompting, just hand it a plugin with brand guidelines. Or for docs, instead of repeated web searches, have it use Serena or Context7.

If you've been running your Claude Code raw, you'll be surprised to see how many hours a week you'll save using the right plugins.

I compiled a huge list of Claude plugins, so you don't have to go through the pain of figuring out what to use and when.

Here's the full list.

Quick answer: best Claude Code plugins by type

What are Claude Code plugins?

Claude Code plugins are packaged extensions for Claude Code. Anthropic describes plugins as bundles that can include skills, agents, hooks, MCP servers, and other capabilities. The official docs say the marketplace lets you discover and install those extensions without building them yourself.

The important shift is packaging. Before plugins, teams often shared scattered CLAUDE.md files, hook scripts, MCP configs, and custom slash commands. Plugins make those pieces installable and shareable through a marketplace or repository.

The plugin is the package. The other pieces are capabilities that can live inside that package.

Resources:

• Anthropic announcement: Customize Claude Code with plugins

• Official directory: Claude plugins

• Installation docs: Discover and install prebuilt plugins

• Plugin reference: Claude Code plugins reference

• Official marketplace repo: anthropics/claude-plugins-official

Plugins vs Skills vs MCP servers vs hooks vs agents

These terms are easy to mix up, but they are not the same thing.

How to install Claude Code plugins

In Claude Code, run:

/plugin

Then use the Discover tab to browse plugins. You can also install a plugin directly:

/plugin install github@claude-plugins-official

The official marketplace is available as claude-plugins-official. Anthropic's docs say the official marketplace is automatically available when you start Claude Code. If a plugin is missing, refresh the marketplace:

/plugin marketplace update claude-plugins-official

For third-party marketplaces like Awesome Claude Plugins, use:

/plugin marketplace add owner/repo-name

For installing directly from the GitHub repo source

git clone <https://github.com/composiohq/awesome-claude-plugins.git>
cd awesome-claude-plugins
claude --plugin-dir ./connect-apps

The command installs Composio Connect MCP which let’s Claude Code securely access all your apps like Jira, Linear, GitHub, and more from a single MCP.

So, let’s check out the best Claude plugins by type.

1. Code intelligence and LSP plugins

Code intelligence plugins give Claude Code access to Language Server Protocol features. That means Claude can jump to definitions, find references, inspect symbols, see diagnostics, and notice type errors after edits. These are the plugins to install first if you work in a typed or large codebase.

Best picks:

• TypeScript LSP for React, Next.js, Node.js, and full-stack JavaScript projects

• Pyright LSP for Python services, FastAPI, Django, Flask, and data tooling

• Rust Analyzer LSP for Rust libraries and services

• Go LSP for Go services and platform tooling

Install one LSP plugin for your main language before adding more complex integrations. It gives Claude a better map of the codebase, making every subsequent workflow safer.

2. MCP integration plugins

MCP integration plugins connect Claude Code to external services. These are useful when the relevant context is outside the repository: issues in Linear, incidents in Slack, deploys in Vercel, errors in Sentry, design specs in Figma, or database state in Supabase.

Best picks:

• GitHub MCP if your work starts from issues, branches, PRs, or repository search

• Linear MCP if your team works from product tickets and acceptance criteria

• Slack MCP if decisions and incident context live in threads

• Vercel MCP if you deploy frontend or Next.js projects there

• Sentry MCP if you want Claude to connect production errors back to code

• Supabase MCP or Firebase if Claude needs backend project context

⚠️ One caveat here, when you install all these MCPs, let’s say you need multiple MCP servers like Linear, GitHub, Supabase, and Vercel. You’d end up choking the LLM context window as they will load all the available tools in the context window. Further uses will gobble up the context more.

This is what Composio solves with

• Dynamic tool loading: As per the context, tools are loaded as and when needed.

• Remote work bench: to let the LLMs chain multiple tools to automate complex workflows.

• Bash tool: to let the LLMs write throw-away codes to handle large files out of the context window.

You can get started within a minute at best at: dashboard.composio.dev

3. Code review plugins

Code review plugins help Claude review changes with more structure. They are useful when you want repeatable checks around tests, types, regressions, simplification, and PR quality.

Best picks:

• Code Review for a broad review workflow

• PR Review Toolkit for reviewing pull requests across comments, tests, errors, types, quality, and simplification

• CodeRabbit if your team already uses CodeRabbit or wants analyzer-heavy review

• Code Simplifier when your codebase needs clarity passes after implementation

Pair these with GitHub for the strongest PR workflow.

4. Security plugins

Security plugins are guardrails for production code. They help Claude notice unsafe patterns while editing or scan the codebase for known classes of vulnerabilities.

Best picks:

• Security Guidance for real-time warnings about risky edits, including command injection, XSS, and unsafe code patterns

• Semgrep for scan-based security checks and rule-driven review

Security Guidance is the better default for most Claude Code users because it works close to the edit loop. Semgrep is stronger when your team already uses static analysis rules or wants a more explicit scan step.

5. Workflow, Git, and automation plugins

Workflow plugins help Claude Code standardize repeated engineering rituals: commit messages, PR creation, repo setup, CLAUDE.md maintenance, hooks, and team-specific automation.

Best picks:

• Commit Commands for clean commits and PR creation

• CLAUDE.md Management for keeping project instructions current

• Claude Code Setup when onboarding Claude Code into an existing codebase

• Hookify when you want to enforce repeated checks or workflow rules

• Feature Dev when you want a more guided exploration, design, and review flow

These are less about one external integration and more about making Claude Code behave consistently across projects.

6. Frontend, browser, and design plugins

Frontend plugins are valuable because UI quality depends on rendered behavior, not just source code. Claude needs access to browser state, design context, screenshots, DOM inspection, and deployment logs to debug real frontend issues.

Best picks:

• Frontend Design for improving UI quality and avoiding generic AI-looking interfaces

• Playwright for end-to-end testing and browser automation

• Chrome DevTools for inspecting live browser behavior

• Figma for design-to-code workflows

• Vercel for deployment, logs, and frontend infrastructure context

For frontend teams, the best stack is TypeScript LSP, Frontend Design, Chrome DevTools, Playwright, GitHub, and Vercel.

7. Memory, context, and codebase-understanding plugins

These plugins help Claude carry context, search code semantically, and pull current docs into the session.

Best picks:

• Context7 when Claude needs version-specific docs and code examples

• Serena when you want semantic code analysis and refactoring support

• Greptile when natural-language repository search is valuable

• Remember when long-running sessions need compressed memory

Do not install every context plugin at once. Start with Context7 for docs lookup, then add a codebase-understanding plugin only if your repo size or architecture demands it.

8. Skills, agents, and plugin-development plugins

Skills and agent plugins package repeatable instructions, specialized workflows, and development helpers. These are useful when you want Claude Code to behave like a more specialized engineering teammate.

Best picks:

• Superpowers if you want a broad upgrade to Claude Code workflows

• Skill Creator if your team wants reusable internal skills

• Plugin Developer Toolkit if you plan to build Claude Code plugins

• MCP Server Dev if you need custom MCP servers for internal tools

These are especially useful for teams standardizing their Claude Code setup across multiple repositories.

9. Composio app automation plugins

Composio's Claude Code plugin is useful when you want Claude Code to act across external apps, not just inspect your repository. It bundles the Composio Connect MCP server with opinionated skills so Claude can search, connect, and act across apps after setup.

The connect-apps plugin lets Claude perform real actions - send emails, create issues, post to Slack. It handles auth and connects to 1000+ apps .

1. Install the Plugin

claude --plugin-dir ./connect-apps-plugin

2. Run Setup

/connect-apps:setup

Paste your API key when asked. (Get a free key at dashboard.composio.dev)

3. Restart & Try It

exit
claude

See all supported apps

Best for:

• Claude Code workflows that need authenticated app actions

• Connecting to tools such as GitHub, Slack, Notion, Gmail, Google Workspace, Linear, and internal APIs

• Teams building agentic workflows that cross product, engineering, docs, and operations tools

Why it matters: a lot of real engineering work happens outside the editor. Issues are in Linear, incidents are in Slack, specs are in Notion, deploys are in Vercel, and customer or operational data can live in many other systems. Composio is valuable when Claude Code needs to operate across the full workspace.

How to choose the right Claude Code plugins

Use a small stack first. Every plugin adds capability, but it can also add setup, permissions, and context overhead.

A good default stack is:

1. One LSP plugin for your main language

2. GitHub for repository and PR context

3. Security Guidance for safety warnings

4. Commit Commands for daily Git workflow

5. One integration for your team's source of truth and cross-app workflow automations, such as Composio

Add more only when you feel a real workflow gap.

Security checklist before installing Claude Code plugins

Before installing a plugin, check:

• Who maintains it?

• Is it Anthropic verified, official, community-maintained, or third-party?

• Does it run commands, open browsers, or install dependencies?

• Does it connect to external services?

• What credentials or scopes does it require?

• Does your team need it enabled globally, or only for one project?

• Can you disable it when the task is done?

• Does the plugin add MCP servers, hooks, or LSP servers you did not expect?

Anthropic's docs warn that plugins and marketplaces are highly trusted components that can execute code with your user privileges. Treat plugins like developer dependencies, especially when they include hooks, shell commands, browser automation, or authenticated MCP servers.

Final recommendation

The best Claude Code plugins are not just the most popular ones. They are the ones that close a specific gap in your workflow.

Start with code intelligence through an LSP plugin. Add GitHub for repository context. Install Security Guidance or Semgrep to make edits safer. Then connect the tools where your team works: Linear, Slack, Vercel, Sentry, Supabase, Figma, Notion, or Composio-powered app workflows.

If you only install five, make them:

• Your main language LSP plugin: TypeScript LSP, Pyright LSP, Rust Analyser LSP, or Go LSP

• Composio

• Security Guidance

• PR Review Toolkit or Code Review

• Commit Commands

That stack gives Claude Code the three things it needs most: better code awareness, safer edits, and access to the context around the work.

FAQs

What is the most installed Claude Code plugin?

In Anthropic's public plugin directory on June 1, 2026, Frontend Design had 829,316 installs, Superpowers had 752,120 installs, and Context7 had 348,660 installs.

What is the best Claude Code plugin?

For most developers, the best first plugin is the Composio plugin, which lets Claude Code interact with the real world and perform cross-app workflows like Linear, Figma, GitHub, Sentry, etc.

How do I install Claude Code plugins?

Run /plugin In Claude Code to browse plugins, or install directly with a command such as:

/plugin install github@claude-plugins-official

What is the official Claude Code plugin marketplace?

The official marketplace is claude-plugins-official. You can browse the public directory at claude.com/plugins.

Are Claude Code plugins the same as MCP servers?

No. A plugin is a package. An MCP server is one capability a plugin can include. A plugin may also include slash commands, hooks, subagents, skills, or LSP support.

Which Claude Code plugins are best for frontend design?

Use TypeScript LSP, Frontend Design, Playwright, Chrome DevTools, GitHub, Vercel, and Figma. That stack gives Claude code intelligence, browser inspection, testing, deployment context, and design context.

Which Claude Code plugins are best for teams?

A practical team stack is GitHub, the relevant LSP plugin, Security Guidance, PR Review Toolkit, Commit Commands, CLAUDE.md Management, and the team's main work-tracking or communication integration, such as Linear or Slack.

Are Claude Code plugins safe?

They can be safe, but they should be reviewed like any other developer dependency. Check the maintainer, permissions, source, external connections, and credentials before installing. Be especially careful with third-party plugins that run shell commands or connect to sensitive tools.