claude-plugins-official: Your Gateway to Claude Code Plugins via MCP

The claude-plugins-official MCP Client provides the authoritative, Anthropic-managed directory for high-quality plugins designed for Claude Code. This Python-based client acts as a central marketplace, allowing developers to discover, install, and manage extensions that augment Claude's capabilities. With 44,562 GitHub stars, it's a significant resource for extending your Claude Code environment.

Navigating the Plugin Landscape

The directory organizes plugins into two distinct categories:

• /plugins: These are internal plugins, developed and maintained directly by Anthropic team members, ensuring a high degree of integration and support.
• /external_plugins: This section hosts third-party plugins contributed by partners and the broader community. These submissions undergo a review process to meet specific quality and security standards before inclusion.

Developers should always exercise caution: Anthropic explicitly states that it does not control the MCP servers, files, or other software included in third-party plugins and cannot guarantee their intended function or immutability. Always review a plugin's homepage and ensure you trust its source before installation.

Installing Plugins in Claude Code

Integrating plugins from claude-plugins-official into Claude Code is straightforward. You can install them directly through Claude Code's built-in plugin system.

To install a specific plugin by name, use the command: /plugin install {plugin-name}@claude-plugins-official

Alternatively, you can browse available plugins interactively within Claude Code by navigating to /plugin > Discover.

Plugin Structure and MCP Integration

Each plugin within the directory adheres to a standard file structure, facilitating consistent development and integration. A key component for MCP interaction is the optional .mcp.json file.

The typical plugin directory structure looks like this:

plugin-name/
├── .claude-plugin/
│   └── plugin.json      # Plugin metadata (required)
├── .mcp.json            # MCP server configuration (optional)
├── commands/            # Slash commands (optional)
├── agents/              # Agent definitions (optional)
├── skills/              # Skill definitions (optional)
└── README.md            # Documentation

The presence of .mcp.json indicates that a plugin is configured to interact with MCP servers, potentially exposing specific functionalities, agents, or skills that Claude Code can leverage. This file is crucial for defining how the plugin's capabilities are exposed over the Model Context Protocol.

For plugins that primarily bundle skills without a .claude-plugin/plugin.json manifest, the marketplace supports a skill-bundle format. This allows direct declaration of skills using strict: false and an explicit skills array within the plugin's definition. An example of such a skill-bundle manifest looks like this:

{
  "name": "example-bundle",
  "description": "Brief description of the bundled skills.",
  "author": { "name": "Author Name" },
  "category": "development",
  "source": {
    "source": "git-subdir",
    "url": "https://github.com/example-org/sdk.git",
    "path": "packages/agent-skills",
    "ref": "main",
    "sha": "<commit sha>"
  },
  "strict": false,
  "skills": [
    "./skill-a",
    "./skill-b",
    "./skill-c"
  ],
  "homepage": "https://github.com/example-org/sdk"
}

This structure enables the marketplace to correctly identify and make available collections of skills that might reside in a larger repository, without requiring a full plugin manifest for each individual skill.

Contributing to the Marketplace

Anthropic encourages contributions to the claude-plugins-official directory.

• Internal Plugins: Developed by Anthropic team members. The /plugins/example-plugin serves as a reference implementation for those looking to understand the internal plugin structure.
• External Plugins: Third-party partners can submit plugins for inclusion. These must adhere to specific quality and security standards. Submissions are made via the plugin directory submission form.

By leveraging the claude-plugins-official MCP Client, developers gain direct access to a curated ecosystem of extensions, enhancing Claude Code's utility and adaptability.

References

• claude-plugins-official on GitHub
• Model Context Protocol Documentation
• claude-plugins-official on model-context-protocol.com