- If you’re still deciding what goes in your plugin, see Decide what to include in your plugin
- If you want to build a small example plugin and submit it, see Build your first plugin
- If you want to share a plugin without a public listing, use your own marketplace for Claude Code or roll it out to your whole organization
- If you came here from Claude Marketplace, the website where you browse plugins, connectors, partner products, and service partners, you’re in the right place: there’s no separate Claude Marketplace submission, and you submit to the directory instead
Before you submit to the directory
A directory listing is either a plugin bundle or an MCP connector.Submit your plugin, and your MCP server as a connector
A plugin bundle is the main thing you submit: one listing that packages whatever the plugin contains, whether that’s skills, an MCP connector reference, commands, agents, or any combination. If you also run the remote MCP server that plugin points at, you submit the server as its own MCP connector too. When you start a submission, the developer portal asks which kind you’re submitting:
If you have a remote MCP server, always submit it as an MCP connector, even when a plugin you’re submitting already references it. Submitting the server as a connector gives your organization the connector’s listing, its dashboard, and the option to pair it with your plugin:
- The connector’s listing: you edit its details and its authentication configuration
- The connector’s dashboard: it shows the server’s health and usage by tool, which a plugin’s Usage tab doesn’t break out
- Pairing with your plugin: when the connector and a plugin bundle that references it are submitted from the same organization, you can pair the two listings
What a listing gets you
A directory listing gives you:- One listing across Claude’s apps: people find it in claude.ai on the web, the desktop and mobile apps, and Cowork, and a plugin they add is also available in their Claude Code sessions
- One developer portal for the whole life of a listing: at claude.ai/directory/manage you submit, follow each submission’s status, publish new versions, see usage, and change or delist the listing. Track your directory submission explains each status
- Updates without resubmitting: after the first submission, you keep the listing current by merging to the tracked branch as you normally release. The directory picks up each commit, scans it, and once it’s published serves it to the people who have your plugin. Update a published plugin covers the steps
- Usage figures: a published plugin’s Usage tab shows installs, versions, how often each skill and MCP server runs, and error rates. A listed connector has a dashboard with server health and usage by tool. Track published plugin usage and Manage your directory listing cover each
Confirm you can submit to the directory
You submit from a claude.ai account, and the listing belongs to the organization you submit from. Before you start, confirm each of these:- Plan: Pro, Max, Team, or Enterprise. Free accounts can’t submit
- Role: on Pro and Max, you submit from your own account and there’s no role to check. On Team and Enterprise, an Owner can submit. On Enterprise, an Owner can also grant the Directory permission to other members through a custom role under Organization settings > Roles. If you don’t have one of those roles, ask an Owner
- Which organization: for a plugin bundle, the first organization to submit a given repository folder holds that listing, and the portal refuses a second organization’s submission of the same one. Submit from the organization that should own the listing long term
Move an earlier submission to the developer portal
A listing you submitted before the developer portal existed stays as it is. Move it to the portal to get what the portal adds:- New versions that the directory scans and, once they’re published, serves to the people who have your plugin
- A status for each submission
- Usage figures for a published plugin
Prepare for review
Anthropic checks every submission before it’s listed, and checks a plugin bundle again with each new version.- Plugin bundles: every version gets automated validation and a security scan, and a person reviews a new listing before it goes live. The plugin pre-submission checklist lists what validation checks
- MCP connectors: every submission is scanned automatically for policy compliance and, by default, listed as a Community connector. Anthropic may escalate a listing to Verified review, in which a reviewer tests each tool against the connector pre-submission checklist
Start a submission in the developer portal
You submit and maintain listings in the developer portal at claude.ai/directory/manage. To start a submission:1
Select Submit new
In the developer portal at claude.ai/directory/manage, select Submit new.
2
Choose the submission type
Under What would you like to submit?, choose Plugin bundle or MCP connector.
3
Follow the checklist and submit pages
Work through the checklist and submit pages for that kind:
- Plugin pre-submission checklist, then Submit a plugin: for a plugin bundle
- Connector pre-submission checklist, then Submit a connector: for an MCP connector
Next steps
These pages cover building and submitting a first plugin and, once a listing is published, maintaining it from the same portal:- Build your first plugin: build a small example plugin and submit it to the directory
- Track your submission: check what your submission’s status means and who acts next
- After publishing: update your server or plugin, and delist
- Track published plugin usage: see installs, versions, runs, and error rates on the plugin’s Usage tab
- Manage your directory listing: for an MCP connector, check health and usage metrics and edit the listing