The plugin directory is a community-driven directory where developers can submit plugins for use in Cowork. This is a separate and complementary directory from the Connectors Directory, which is specific to MCP connectors.
Getting your plugin to users
Once you’ve built a plugin, there are several ways to get it to users:
- Direct install — You can install specific plugins yourself, or guide select users to install them. This is the simplest path for internal tools or small teams.
- Your own plugin marketplace — You can serve your own plugin marketplace, which allows a subset of opted-in users to access any plugin you share. This is a great fit for enterprise contexts or communities with shared tasks. See the Claude Code docs on sharing a marketplace for setup instructions.
- Submit to the Claude plugin directory — You can submit to the Claude plugin directory, which is made available to all users of Cowork and Claude Code.
Plugins are submitted by developers and creators in the community. Anthropic performs basic automated review on submissions before adding them to the directory. Plugins with an “Anthropic Verified” badge have undergone additional review from a quality and safety perspective. That said, there are limits to what Anthropic is able to review — you should only install plugins from developers you trust.
There are no guarantees that any community plugin will become Anthropic Verified.
Exercise caution when installing community plugins. Always review a plugin’s permissions, connected services, and data access before use.
What makes a good plugin
The best plugins bundle related capabilities together into a coherent package that solves a specific job function or workflow end-to-end. Rather than exposing a single tool, a good plugin combines skills, connectors, slash commands, and sub-agents so Claude has everything it needs to handle a category of work.
For example, a sales plugin might bundle a CRM connector, a skill that teaches Claude your sales process, slash commands for common tasks like prospect research and call follow-ups, and a sub-agent that handles competitive analysis in parallel. Together, these components make Claude a specialist — individually, they’re just building blocks.
Plugins can include any combination of:
- Skills — Task-specific instructions that Claude activates dynamically based on context
- MCP connectors — Connections to external tools and data sources. Plugins can contain any MCP, including remote MCPs, local MCPs, and MCPBs. The MCP configuration within a plugin is highly customizable.
- Slash commands — User-invoked commands for triggering specific workflows
- Sub-agents — Custom agent definitions for delegating complex work
Guiding Claude through MCP setup
Plugins can include a SETUP.md skill to guide Claude through configuring and connecting any MCP servers bundled in the plugin. This lets you define step-by-step setup instructions that Claude follows when a user installs or activates your plugin.
Using safe MCP connectors in plugins
While a plugin can include any MCP of any kind in its .mcp.json definition, we strongly encourage using connectors that already exist in the Connectors Directory or come from well-known developers. This will increase the likelihood of verification and will reduce the number of warnings shown to users.
Directory terms & conditions
All plugins in the directory must comply with:
Security
Each plugin in the directory includes a link to where you can review its contents before installing. Plugins are capable of loading remote MCP servers, local MCP servers, and other local software tools to assist you in doing work. You should review any additional software that may be installed by a plugin, as community plugins may install unverified, third-party software that could be malicious or result in unintended behavior.
Best practices when using community plugins:
- Review the plugin’s source code before installing
- Check which MCP connectors are included and what permissions they request
- Prefer Anthropic Verified plugins for production workflows
- Report any suspicious activity to Anthropic
Submitting your plugin
To submit a plugin to the directory, you can either share a GitHub link or upload a zip file containing your plugin (with all folder structures inside).
Submit your plugin using the plugin directory submission form.
Any changes to your plugin after submission will require re-submitting the form, as each new submission or update is scanned before being shared in the directory. 
