Purpose
Plugins are the main way to build third-party extensions for Claude. A plugin packages MCP connectors, Agent Skills, or both, and approved plugins are listed in the Claude directory. This skill walks a developer from "what should I ship?" to a published listing, using only what the announcement states. Portal and directory details are summarized in references/submission-portal.md.
When to use
- A developer wants Claude users to discover and install their integration.
- Someone must choose between submitting one MCP connector and a full plugin bundle.
- A team is preparing for review and wants to know what is checked.
- A publisher wants to know what analytics exist after launch.
Instructions
Check eligibility. The submission portal is open to developers on paid Claude plans.
Decide what the extension is.
- Only a remote MCP server → submit a single MCP connector by pointing the portal at the remote server.
- Several MCP servers and/or skills → submit a plugin bundle hosted on GitHub.
- Targeting Claude Code as well → the bundle may also carry LSPs, commands, hooks, and agents.
Consider the MCP 2.0 extensions. Claude supports the latest MCP spec with its stateless core.
- MCP Apps — interactive UI rendered in the chat.
- Enterprise Managed Auth — zero-touch OAuth for enterprise users. Use them when the extension needs UI in chat or enterprise sign-in without per-user OAuth steps.
Submit and read the results. On submit, the portal validates the plugin automatically and runs a safety scan. Track review status, scan results, and recommended changes in the portal and address the recommendations before resubmitting.
Publish on your schedule. Approval does not publish automatically; the developer chooses when to publish the listing.
Measure after launch. Usage analytics show installs by product surface and by version. Discovery metrics show listing views and the searches that led to them. Use them to decide what to improve in the listing or the next version.
Do not rebuild existing work. Existing skills, connectors, and plugins need no changes. A single discovery experience is rolling out across Claude and Claude Code; skills and connectors stay as building blocks the directory keeps listing, and turning a connector listing into a plugin is planned for later. For build specifics, refer to the official plugin build docs linked from the original post.
Examples
- Developer: "I only have a hosted MCP server for our ticketing API." → Submit a single MCP connector pointing at the remote server; no GitHub bundle is needed.
- Developer: "We have two MCP servers and three skills, plus a hook for Claude Code users." → Package them as one GitHub-hosted plugin bundle; hooks are allowed in Claude Code bundles.
- Developer: "We want a dashboard widget in the chat and SSO-friendly auth for enterprise customers." → Use MCP Apps for the interactive UI and Enterprise Managed Auth for zero-touch OAuth.
- Developer: "Our listing gets views but few installs." → Check discovery metrics (which searches lead to the listing) against installs by surface and version, then revise the listing or the release.