Claude Code Plugins Official Directory
A practical guide to Anthropic's official Claude Code plugin directory, its repository structure, install command, trust model, and use cases.
Claude Code Plugins Directory: Official Plugin Reference
Key takeaways#
anthropics/claude-plugins-officialis Anthropic's official directory for Claude Code plugins.- The repository separates Anthropic-maintained plugins in
/pluginsfrom partner and community submissions in/external_plugins. - Installation uses Claude Code's plugin system:
/plugin install {plugin-name}@claude-plugins-officialor/plugin > Discover. - Each plugin can include metadata, commands, agents, skills, hooks, and MCP servers, so users should review trust and security before installation.
- This is a reference resource for Claude Code users, not a standalone SaaS product.
What this resource is#
The Claude Code Plugins Directory is a curated GitHub repository that points Claude Code users toward plugins that have been accepted into Anthropic's official plugin marketplace. The repository README describes it as a directory of high-quality Claude Code plugins. It is managed under the anthropics GitHub organization and links to the official Claude Code plugin documentation.
The directory matters because Claude Code plugins are more than a theme or small preference file. A plugin can ship commands, agents, skills, hooks, and MCP server configuration. That means a plugin can change how a local coding assistant behaves, what tools it calls, what MCP servers it can configure, and what context it sees. Treating the directory as a trusted entry point helps developers find useful plugins while still keeping review discipline.
Repository structure#
The repository uses two top-level plugin areas. /plugins contains internal plugins developed and maintained by Anthropic. /external_plugins contains third-party plugins from partners and the wider community. This split is useful when evaluating trust: an internal plugin comes from Anthropic, while an external plugin should be reviewed as third-party code even if it appears in the official directory.
The README also documents a standard plugin structure. A plugin includes a .claude-plugin/plugin.json metadata file. It may also include commands/, agents/, skills/, and README.md; MCP servers are configured through .mcp.json, and hooks can be declared through supported hook configuration such as hooks/hooks.json or inline plugin metadata. Builders should inspect these files before installing a plugin in a real work environment.
How to install plugins#
Claude Code users can install plugins directly through the Claude Code plugin system. The README gives the command pattern /plugin install {plugin-name}@claude-plugins-official. Users can also browse from /plugin > Discover inside Claude Code.
A safe workflow is to open the plugin folder in GitHub first, read the metadata, check whether it includes hooks or MCP servers, and then install it in a low-risk project. If the plugin touches files, shells out to tools, or connects to external services, test it before using it on private repositories.
Who should use it#
Use this directory if you already use Claude Code and want a starting point for vetted plugin discovery. It is especially useful for engineers building repeatable workflows around code review, documentation, testing, or project-specific agents.
Do not treat the directory as a replacement for security review. Anthropic's README explicitly warns users to trust a plugin before installing, updating, or using it. That warning is important because plugins can include third-party software, MCP servers, and other moving parts that Anthropic may not control.
Related entities#
This resource is attached to Claude Code because plugins extend Claude Code behavior. It is also linked to Anthropic as the organization that manages the repository and documentation.