Anthropic launches official plugin directory for Claude Code

Anthropic has launched an official plugin directory for Claude Code, its terminal-based coding agent. According to a write-up on dev.to, the directory is hosted in the anthropics/claude-plugins-official repository on GitHub and acts as the company's first-party hub for adding new capabilities and integrations to the tool.

What the directory contains

The repository is organised into two areas. Plugins created by Anthropic's own team live under /plugins, while contributions from partners and the broader community are kept in /external_plugins. External developers and partners can package their own collections of tools or skills and submit them for inclusion in the official marketplace, provided they meet Anthropic's quality and security requirements.

How a plugin is put together

According to dev.to, each plugin follows a conventional layout. Metadata is mandatory and stored in a plugin.json file inside a .claude-plugin directory. Beyond that, a plugin can optionally ship a .mcp.json file for configuring Model Context Protocol servers, a commands/ folder for slash commands, an agents/ folder for agent definitions, and a skills/ folder for skill definitions, typically accompanied by a README for documentation.

One design detail is worth noting: plugin names are treated as immutable identifiers. The dev.to article explains this is deliberate, meant to prevent installations from failing when a plugin is renamed.

Installing a plugin

There are two ways to get started. Users can run /plugin install {plugin-name}@claude-plugins-official directly inside Claude Code, or browse the available options through the Discover section of the /plugin menu.

Trust remains with the user

The directory centralises discovery, but not accountability. Anthropic does not control the code inside third-party MCP servers or plugin files, and says so explicitly. The dev.to write-up advises developers to verify a plugin's details and be confident in it before installing or updating, meaning vetting third-party code is still a manual step left to the person pressing install.

Why it matters

A first-party directory gives Claude Code the marketplace-style distribution model that turned code editors into extensible platforms, lowering the barrier for developers who want to tailor their agent and giving plugin authors a visible channel to reach users. The directory layout also shows where Anthropic sees the product surface expanding: MCP server integrations, custom slash commands, agents and skills are all treated as first-class, installable building blocks rather than ad hoc configuration.

At the same time, the security caveat deserves attention. Coding agents execute commands, read files and connect to external services, so installing a third-party plugin effectively grants code a foothold in a developer's environment. An official-sounding directory can create a false sense of vetting, and Anthropic's own disclaimer makes clear that the responsibility for reviewing what gets installed stays with the user. The immutable naming scheme, meanwhile, is a small but telling fix for a familiar operational problem — broken installs caused by renamed packages — that larger package ecosystems have wrestled with for years.