Where Is the Master Plugin Registry in the Claude Plugins Community Repository?

The master plugin registry is stored in the JSON file .claude-plugin/marketplace.json at the root of the repository.

The anthropics/claude-plugins-community repository hosts community-contributed extensions for Claude Code. Central to this ecosystem is the master plugin registry, which maintains the authoritative list of all available plugins and their metadata configurations required by the tooling.

Understanding the Registry File Structure

Primary Registry Location

According to the anthropics/claude-plugins-community source code, the master plugin registry resides at .claude-plugin/marketplace.json in the repository root. This JSON file serves as the single source of truth for all community-contributed Claude plugins, containing their metadata, capabilities, and configuration parameters.

Registry Schema Overview

The marketplace.json file organizes plugins as a structured collection. Each entry defines the plugin's identity, version compatibility, and execution context. The Claude Code tooling parses this file to populate its internal plugin marketplace and validate available extensions.

How to Access the Master Plugin Registry

Inspecting the Registry Locally

When working with a local clone of the repository, you can inspect the registry contents using standard Unix tooling and jq for JSON parsing.

# Count total plugins in the registry

cat .claude-plugin/marketplace.json | jq '.plugins | length'

This command reads the master plugin registry and returns the total number of registered plugins, useful for verifying repository state or generating statistics.

Fetching the Registry Remotely

For integrations that query the latest registry without cloning the entire repository, fetch the raw JSON directly from GitHub.

# List all plugin keys from the remote registry

curl -s https://raw.githubusercontent.com/anthropics/claude-plugins-community/main/.claude-plugin/marketplace.json | jq '.plugins | keys'

This approach allows automated tooling to discover new plugins or validate manifests against the current master plugin registry state.

Supporting Configuration Files

Individual Plugin Manifests

While .claude-plugin/marketplace.json acts as the master index, individual plugins use the template defined in .claude-plugin/plugin.json. This file specifies the required schema for plugin metadata, including fields for name, description, entry points, and permission scopes. Contributors copy this template into their plugin directories and customize it for their specific implementation.

Skill-Specific Registries

The repository demonstrates scoped registry patterns for organizing plugins by domain. The quickdesign skill maintains its own subdirectory registry at quickdesign/.claude-plugin/marketplace.json, illustrating how the master plugin registry architecture supports both global and skill-specific plugin collections while maintaining schema consistency.

Summary

• The master plugin registry is located at .claude-plugin/marketplace.json in the repository root.
• Use jq filters like .plugins | length or .plugins | keys to query registry contents programmatically.
• The .claude-plugin/plugin.json file provides the template schema for individual plugin manifests.
• Subdirectories can host skill-specific registries following the same JSON structure as the master file.

Frequently Asked Questions

What is the exact file path for the master plugin registry?

The master plugin registry is located at .claude-plugin/marketplace.json relative to the repository root. This path serves as the hardcoded authoritative source that Claude Code tooling references to discover and load community plugins.

How do I count the number of plugins in the registry?

Pipe the registry contents through jq to count plugins efficiently. Execute cat .claude-plugin/marketplace.json | jq '.plugins | length' from the repository root to retrieve the total count without manually parsing the JSON structure.

What is the difference between marketplace.json and plugin.json?

The marketplace.json file is the master plugin registry containing the complete catalog of all available plugins, while plugin.json in the .claude-plugin directory functions as a template manifest. Individual plugin contributors use this template to structure their own plugin.json files, ensuring consistent metadata formatting across the ecosystem.

Can I create sub-registries for specific skills?

Yes, the repository architecture supports nested registries scoped to specific skills or domains. The quickdesign/.claude-plugin/marketplace.json path demonstrates this pattern, showing how skill-specific collections can maintain their own plugin registries while adhering to the same schema standards as the master file.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}