Recommended Claude Code Plugins | Complete Category List and How to Choose

Complete Plugin Reference — All 29 Official Marketplace Plugins

While other articles scatter plugins across multiple small category tables, this article presents all official marketplace plugins in a single comparable table. Here is how to read it: "Recommended" indicates how immediately useful a plugin is for a professional developer's daily work, on a three-tier scale — ★★★ means "install first," ★★ means "needed depending on the project," and ★ means "specific use cases only." The "Required binaries / dependencies" column lists what must be installed beforehand; plugins with an empty cell require no additional binaries (Source: Discover and install plugins from the marketplace).

All 29 rows in the table have been verified against the official documentation. As of May 2026, the marketplace contains no community-submitted plugins — every plugin is official and managed by Anthropic. Distributing plugins within an organization by registering a private marketplace is possible, but this article covers only official plugins.

Code Intelligence Category — Start with One LSP Plugin for Your Language

The category that Anthropic itself suggests as the first thing to install is Code Intelligence. These plugins connect Claude Code to a language server via the Language Server Protocol (LSP), enabling automatic type error detection, go-to-definition, and reference search immediately after editing a file. It is the same technology that powers code intelligence in VS Code, now made available from within Claude Code (Source: Discover and install plugins from the marketplace).

Once a plugin is installed and the language server binary is available, Claude gains two capabilities. The first is automatic diagnostics: every time Claude edits a file, the language server analyzes the change and automatically reports type errors, missing imports, and syntax issues. Problems can be detected and fixed within the same turn, without manually running the compiler. The second is code navigation: go-to-definition, reference search, hover type info, symbol listing, and call hierarchy tracing all become available, providing more accurate navigation than grep-based search.

# For a Python project, your very first command
/plugin install pyright-lsp@claude-plugins-official
/reload-plugins

After installation, when Claude edits a file, a "diagnostics found" indicator appears. Press Ctrl+O to view the diagnostics inline.

Decision Criteria and Pitfalls for LSP Plugins

If the Errors tab shows "Executable not found in $PATH" after installing a plugin, it means the binary listed in the "Required binaries / dependencies" column of the table is not installed. Install the binary first — for example brew install pyright, npm i -g typescript-language-server, or rustup component add rust-analyzer — then check again.

Memory consumption is also worth considering. rust-analyzer can consume several gigabytes on large projects. If it becomes too heavy, disabling it temporarily with /plugin disable rust-analyzer-lsp@claude-plugins-official and falling back to Claude's built-in search is a practical approach. In monorepo environments, the language server may misidentify the workspace and produce false-positive diagnostics, but this does not affect the accuracy of code edits.

External Integration MCP Category — Close the Development Loop by Connecting to Your Work Tools

For professional use of Claude Code, connecting directly to work tools via external integration MCP (Model Context Protocol) plugins is where the real value lies. Each plugin bundles a pre-configured MCP server, so authentication and tool definitions are complete with just the plugin installation — no need to manually configure an MCP server, which is the biggest advantage (Source: Discover and install plugins from the marketplace).

The official marketplace offers 12 external integration plugins: source control (github / gitlab), project management (atlassian / asana / linear / notion), design (figma), infrastructure (vercel / firebase / supabase), communication (slack), and monitoring (sentry). If your team uses any of these services, they are well worth installing right away.

The priority order depends on your workflow, but for most engineers the sequence in which impact is most tangible is as follows. First choice is github — since it lets you create PRs, manage Issues, and conduct code reviews directly from Claude, it is essential in almost every development environment. Second choice is linear or atlassian, embedding the core of ticket-driven development into Claude. Third choice is slack, pulling team communication into Claude so that thread summaries and status reports can be automated. Fourth choice is sentry, which connects production errors directly to fix tasks and directly reduces Mean Time To Recovery (MTTR).

/plugin install github@claude-plugins-official
/plugin install linear@claude-plugins-official
/plugin install slack@claude-plugins-official
/reload-plugins

Authentication Setup When Installing MCP Plugins

The OAuth tokens or API keys that each plugin requires will be prompted on first use. Having them ready in advance makes the initial setup smoother. The github plugin requires a GitHub Personal Access Token (PAT) with the repo scope; linear requires a Linear API key; slack requires a Slack User OAuth Token. Permissions are checked with scopes at plugin installation time, so issuing tokens with the minimum necessary scopes is recommended. For example, if you only need read access with the github plugin, using read:repo alone reduces security risk by following the principle of least privilege.

Development Workflow Category — Automating Git Operations and an Entry Point for Custom Plugins

Four plugins are available to delegate frequently recurring operations in daily development to Claude. The goal is to reduce simple repetitive tasks and improve operational efficiency (Source: Discover and install plugins from the marketplace).

commit-commands is the most highly recommended plugin in this category. Running /commit-commands:commit causes Claude to check changes with git status / git diff, generate an appropriate commit message, and execute git add + git commit. Running /commit-commands:push extends this through to a push to the remote, and /commit-commands:pr goes all the way to creating a pull request with a description following the PR template. Engineers who previously typed git add . && git commit -m "..." && git push && gh pr create by hand will feel the biggest impact.

pr-review-toolkit invokes a set of agents each specialized in a different review perspective — security, performance, readability, and more — making it useful for self-review before submitting a large change. agent-sdk-dev provides tooling for building custom agents with the Claude Agent SDK and is unnecessary until you are familiar with the SDK. plugin-dev is a toolkit that generates scaffolding for custom plugins (SKILL.md / plugin.json / marketplace.json), serving as the entry point for contributing to the official marketplace.

Output Style Category — For Educational and Learning Purposes Only

Two plugins are available to customize how Claude responds. explanatory-output-style provides responses with educational insight into implementation choices, and learning-output-style provides an interactive learning mode for skill building (Source: Discover and install plugins from the marketplace).

If your sole purpose is writing code for work, these are unnecessary — but they are effective for internal training, onboarding new employees, or personal learning. After installation, responses tend to become longer, so weigh the trade-off against context consumption before installing. A practical approach is to consider these only when you have a comfortable context budget available on a Pro or Max plan.

Plugin Command Reference

This section covers every relevant command from plugin installation through management and team distribution. Note that both CLI commands (claude plugin ...) and in-session slash commands (/plugin ...) are available (Source: Discover and install plugins from the marketplace).

When enforcing a consistent plugin configuration across an entire team, the standard approach is to use project scope by adding extraKnownMarketplaces and enabledPlugins to .claude/settings.json. Using user scope for personal projects and project scope for production team environments keeps the configuration consistent.

Troubleshooting Q&A

Here are common issues encountered when installing plugins, organized by symptom, along with steps for resolution based on the official documentation troubleshooting section (Source: Discover and install plugins from the marketplace).

Summary: Prioritization Framework

Finally, here is a prioritized installation order for professional use. There is no need to install all 29 plugins at once — building up incrementally is the practical approach.

Stage 1: One immediate-impact Code Intelligence plugin. Install just one *-lsp plugin for your primary language. If the language server binary is already installed, automatic type error detection will be working within five minutes. Simply eliminating the need to manually run the compiler will visibly improve Claude's ability to fix issues accurately.

Stage 2: External integration MCPs for direct connection to work tools. github is essential for anyone using it in development. Adding linear or atlassian, slack, and sentry makes the entire development cycle operable from Claude.

Stage 3: Workflow efficiency. Use commit-commands to consolidate commit-through-PR creation into a single command. If you want to try building your own plugin, add plugin-dev. Output style plugins can be deferred without any issue if your goal is professional development.

After installation, always activate with /reload-plugins and call commands using the namespaced syntax /<plugin-name>:<command>. On the security side, consider blocking untrusted third-party marketplaces using the admin setting strictKnownMarketplaces. Because plugins can execute arbitrary code on your machine with user-level privileges, always verify the trustworthiness of the source before installing.

Sources (Primary Information)

• Discover and install plugins from the marketplace (Claude Code official)
• Create and distribute plugin marketplaces (Claude Code official)
• Create plugins (Claude Code official)
• Language Server Protocol specification (Microsoft)

Related Articles

• The structure and creation of the Claude Code Marketplace
• Introduction to Claude Code — 9 features anyone can use
• What the 4 official Claude plugins and custom plugins unlock
• What is Claude MCP — capabilities overview and 5 connection steps
• Getting started building Claude Skills — the minimal SKILL.md approach