Claude Code has a plugin marketplace now: what you can install, how to install it, and what to watch out for

Sat, 23 May 2026 19:03:30 +0800

anthropics/claude-plugins-official is the official Claude Code plugin directory managed by Anthropic. It is not just a normal code repository. It is a marketplace that Claude Code’s plugin system can use directly, collecting Claude Code plugins maintained or curated by Anthropic.

This repository matters because Claude Code is moving from “an AI coding command-line tool” toward “an extensible development environment.” Plugins can package Skills, Agents, Hooks, MCP servers, LSP servers, background monitors, and default settings so teams and communities can distribute them in a consistent way.

What is this repository?

The README describes it directly: it is a curated directory of high-quality Claude Code plugins.

The directory is mainly split into two parts:

/plugins: plugins developed and maintained internally by Anthropic.
/external_plugins: third-party plugins from partners and the community.

In other words, it contains both official capabilities and curated external ecosystem entries. For regular users, the direct value is that plugins can be discovered and installed through Claude Code’s /plugin system. For developers, it is a useful window into Claude Code’s plugin format and ecosystem direction.

How to install plugins

The README gives a simple installation command. You can install directly through Claude Code’s plugin system:

`1`	`/plugin install {plugin-name}@claude-plugins-official`

You can also open the plugin discovery entry inside Claude Code:

`1`	`/plugin > Discover`

The key part is @claude-plugins-official, which refers to the official plugin marketplace. According to the Claude Code documentation, claude-plugins-official is the official marketplace maintained by Anthropic and is available by default in Claude Code installations.

What does a plugin look like?

The repository README shows a standard plugin structure:

plugin-name/
├── .claude-plugin/
│   └── plugin.json
├── .mcp.json
├── commands/
├── agents/
├── skills/
└── README.md

.claude-plugin/plugin.json is the metadata file, usually declaring the plugin name, description, version, author, and related fields. Other directories are optional and depend on what the plugin provides:

skills/: instructions for skills Claude can invoke automatically.
commands/: slash commands.
agents/: custom agent definitions.
hooks/: event-triggered logic.
.mcp.json: MCP server configuration.
.lsp.json: language server configuration.
monitors/: background monitor configuration.
settings.json: default settings shipped with the plugin.

This means a Claude Code plugin is not one single kind of extension. It is a packaging format. A plugin can be a tiny command, or it can be an entire workflow for a specific stack.

What directions are already in the official directory?

The /plugins directory already covers many development scenarios, including:

LSP plugins: typescript-lsp, pyright-lsp, rust-analyzer-lsp, gopls-lsp, clangd-lsp, csharp-lsp, jdtls-lsp, kotlin-lsp, lua-lsp, php-lsp, ruby-lsp, swift-lsp.
Programming workflows: code-review, feature-dev, code-modernization, code-simplifier, commit-commands, pr-review-toolkit.
Claude Code configuration and plugin development: claude-code-setup, claude-md-management, plugin-dev, skill-creator, mcp-server-dev.
Output styles and specialized capabilities: explanatory-output-style, learning-output-style, security-guidance, session-report, math-olympiad.

The /external_plugins directory points toward more third-party tools and services, such as github, gitlab, linear, asana, firebase, playwright, terraform, context7, serena, telegram, and discord.

Together, these plugins suggest a trend: Claude Code does not only want to edit files. It also wants to connect with code intelligence, project management, cloud services, testing, infrastructure, and team collaboration tools.

Why the plugin system matters

Previously, many Claude Code customizations could live inside a project’s .claude/ directory, such as commands, agents, skills, or hooks. That works for personal workflows or one project, but it is not ideal for reuse across projects or consistent team distribution.

Plugins solve the reuse and distribution problem:

The same configuration can be installed across multiple projects.
Commands and skills are namespaced, reducing conflicts.
Plugins can be published and updated through a marketplace.
Teams can package internal best practices as standard plugins.
The community can maintain extensions for specific frameworks, languages, or services.

This resembles VS Code extensions, JetBrains plugins, or browser extensions. Once a tool has a stable plugin ecosystem, it is no longer just a single product; it starts becoming a platform.

What does it mean for developers?

If you are only a Claude Code user, the most practical use of this repository is finding plugins. For example, if you need LSP support for TypeScript, Python, Rust, or Go, you can first check whether the official directory already has the corresponding plugin. If you need PR review, commit helpers, or code modernization workflows, the official plugins are also a good starting point.

If you develop plugins, this repository is more like a reference library. You can study its directory layout, plugin.json style, README structure, and how Anthropic combines skills, agents, MCP, LSP, and hooks.

The Claude Code documentation also gives a clear guideline: use .claude/ for single-project customization, but turn it into a plugin when you want to share it with a team, reuse it across projects, version releases, or distribute it through a marketplace.

Security boundaries matter

The repository README opens with an important warning: make sure you trust a plugin before installing, updating, or using it. The reason is simple. A plugin may include MCP servers, files, scripts, or other software. Anthropic maintaining the directory does not mean every plugin will behave exactly as expected in your local environment.

In practice, it is worth doing at least a few checks:

Read the plugin homepage and README before installing.
Check whether it includes .mcp.json, hooks, executable scripts, or background monitors.
Be extra careful with plugins that access accounts, code repositories, chat tools, or cloud services.
Test plugins in a sandbox or test repository before enabling them in important projects.
In team environments, review plugin sources and versions centrally.

AI coding plugins often have much higher privileges than ordinary editor themes. They may read project files, call external services, start local commands, or affect commit and deployment flows. Treat the trust boundary more strictly than “installing a small tool.”

Relationship with the community marketplace

The Claude Code documentation says Anthropic maintains two public plugin marketplaces:

claude-plugins-official: a curated set of plugins maintained by Anthropic.
claude-community: a community plugin directory where third-party submissions go through review.

They have different roles. Community plugins can enter the review pipeline through submission forms. The official directory is curated separately by Anthropic, with no public application process. In short, claude-plugins-official is closer to an official curated directory, while claude-community is the open community directory.

Summary

The significance of anthropics/claude-plugins-official is not merely that another GitHub repository exists. It shows Claude Code’s extension mechanism becoming platform-like: Skills, Agents, Hooks, MCP, LSP, background monitors, and default settings can now be packaged, installed, updated, and distributed.

For individual developers, the official plugin directory can lower the cost of configuring Claude Code. For teams, it offers a way to standardize internal workflows. For plugin developers, it shows the plugin structure and ecosystem direction Anthropic is endorsing.

The next thing to watch is not just any single plugin, but whether the Claude Code plugin ecosystem forms stable layers: official curated plugins, community plugins, private team marketplaces, and specialized extensions for mainstream languages, frameworks, and SaaS services. If that path works, Claude Code will look more and more like a programmable AI development platform, not just a command-line assistant.

References:

GitHub project: https://github.com/anthropics/claude-plugins-official
Claude Code plugin documentation: https://code.claude.com/docs/en/plugins

Plugins on KnightLi Blog