Publish to the directory changeddirectory/publish
Nearest release: v2.1.288, published an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 2 Oct 2026 20:03 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+20added
Lines−20removed
From line
10
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits7to this page, all time
The whole hunk
from line 10, old and new numbered
/
from line 10
1010
1111> [!NOTE]
1212>
13> * If you're still deciding what goes in your plugin, see [Decide what to include in your plugin](/docs/connectors/building/what-to-build)
14> * If you want to build a small example plugin and submit it, see [Build your first plugin](/docs/plugins/quickstart)
15> * If you want to share a plugin without a public listing, use [your own marketplace](https://code.claude.com/docs/en/plugins/publish) for Claude Code or [roll it out to your whole organization](/docs/plugins/org-rollout)
13> * If you're still deciding what goes in your plugin, see [Decide what to include in your plugin](/docs/connectors/building/what-to-build.md)
14> * If you want to build a small example plugin and submit it, see [Build your first plugin](/docs/plugins/quickstart.md)
15> * If you want to share a plugin without a public listing, use [your own marketplace](https://code.claude.com/docs/en/plugins/publish) for Claude Code or [roll it out to your whole organization](/docs/plugins/org-rollout.md)
1616> * If you came here from [Claude Marketplace](https://claude.com/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
1717
1818## Before you submit to the directory
from line 48
4848
4949Work through the checklist and submit pages for that kind:
5050
51* [Plugin pre-submission checklist](/docs/plugins/pre-submission-checklist), then [Submit a plugin](/docs/plugins/submit): for a plugin bundle
52* [Connector pre-submission checklist](/docs/connectors/building/review-criteria), then [Submit a connector](/docs/connectors/building/submission): for an MCP connector
51* [Plugin pre-submission checklist](/docs/plugins/pre-submission-checklist.md), then [Submit a plugin](/docs/plugins/submit.md): for a plugin bundle
52* [Connector pre-submission checklist](/docs/connectors/building/review-criteria.md), then [Submit a connector](/docs/connectors/building/submission.md): for an MCP connector
5353
5454## Submit your plugin, and your MCP server as a connector
5555
from line 69
6969
7070For your own product, make two submissions: the server as an MCP connector, then the plugin bundle whose skills teach Claude how to use it. Point the bundle's MCP server configuration at the same URL, so people who have both see one set of tools rather than two.
7171
72Desktop extension listings in the directory are deprecated, and the directory no longer accepts local MCP servers packaged as desktop extensions (MCPB). To distribute a local MCP server through the directory, include it in a plugin bundle. [Compare component support by app](/docs/plugins/platform-support#compare-component-support-by-app) shows where a plugin's local servers run.
72Desktop extension listings in the directory are deprecated, and the directory no longer accepts local MCP servers packaged as desktop extensions (MCPB). To distribute a local MCP server through the directory, include it in a plugin bundle. [Compare component support by app](/docs/plugins/platform-support.md#compare-component-support-by-app) shows where a plugin's local servers run.
7373
7474Skills aren't a submission type on their own. Put them in a bundle.
7575
from line 77
7777
7878Anthropic checks every submission before it's listed, and checks a plugin bundle again with each new version.
7979
80* **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](/docs/plugins/pre-submission-checklist) lists what validation checks
81* **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](/docs/connectors/building/review-criteria)
80* **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](/docs/plugins/pre-submission-checklist.md) lists what validation checks
81* **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](/docs/connectors/building/review-criteria.md)
8282
8383Every listing is subject to the [Anthropic Software Directory Terms](https://support.claude.com/en/articles/13145338-anthropic-software-directory-terms) and [Software Directory Policy](https://support.claude.com/en/articles/13145358-anthropic-software-directory-policy).
8484
85There's no separate application for the **Verified** label or for where in the directory a listing is placed. Anthropic decides both during review, and [Connector verification](/docs/connectors/verification#list-your-own-connector) explains how a listing becomes Verified and what each label means to people installing it.
85There's no separate application for the **Verified** label or for where in the directory a listing is placed. Anthropic decides both during review, and [Connector verification](/docs/connectors/verification.md#list-your-own-connector) explains how a listing becomes Verified and what each label means to people installing it.
8686
87Review time isn't fixed. Your submission's current state shows in the portal, and [Track your directory submission](/docs/directory/submission-status) explains what each status in the portal means and who acts next.
87Review time isn't fixed. Your submission's current state shows in the portal, and [Track your directory submission](/docs/directory/submission-status.md) explains what each status in the portal means and who acts next.
8888
8989## Move an earlier submission to the developer portal
9090
from line 97
9797The earlier Claude Console form for plugin submissions is no longer supported. To move a submission you made through it, open [**Plugin submissions**](https://platform.claude.com/plugins/submissions) in the Claude Console:
9898
9999* **A submission with a Withdraw button**: select **Withdraw**. Then submit the plugin again at [claude.ai/directory/manage](https://claude.ai/directory/manage) from a claude.ai account
100* **A submission with no Withdraw button**: email `[email protected]` to have it moved to the developer portal instead of starting a new submission there. If you already saved a draft in the developer portal for the same repository and folder, [delete the draft](/docs/plugins/submit#withdraw-or-delist-a-plugin) first
100* **A submission with no Withdraw button**: email `[email protected]` to have it moved to the developer portal instead of starting a new submission there. If you already saved a draft in the developer portal for the same repository and folder, [delete the draft](/docs/plugins/submit.md#withdraw-or-delist-a-plugin) first
101101
102102Until the Console submission is withdrawn or moved, the portal can refuse **Submit for review** for the same repository and folder with **Already submitted by another organization**.
103103
from line 105
105105
106106A directory listing gives you:
107107
108* **One listing across Claude's apps**: you submit once, and the listing appears in each app that [supports what your plugin contains](/docs/plugins/platform-support)
109* **One developer portal for the whole life of a listing**: at [claude.ai/directory/manage](https://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](/docs/directory/submission-status) explains each status
110* **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](/docs/plugins/submit#update-a-published-plugin) covers the steps
111* **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](/docs/connectors/building/after-publishing#track-published-plugin-usage) and [Manage your directory listing](/docs/connectors/building/managing-your-listing) cover each
108* **One listing across Claude's apps**: you submit once, and the listing appears in each app that [supports what your plugin contains](/docs/plugins/platform-support.md)
109* **One developer portal for the whole life of a listing**: at [claude.ai/directory/manage](https://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](/docs/directory/submission-status.md) explains each status
110* **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](/docs/plugins/submit.md#update-a-published-plugin) covers the steps
111* **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](/docs/connectors/building/after-publishing.md#track-published-plugin-usage) and [Manage your directory listing](/docs/connectors/building/managing-your-listing.md) cover each
112112
113113## Next steps
114114
115115These pages cover building and submitting a first plugin and, once a listing is published, maintaining it from the same portal:
116116
117* [Build your first plugin](/docs/plugins/quickstart): build a small example plugin and submit it to the directory
118* [Track your submission](/docs/directory/submission-status): check what your submission's status means and who acts next
119* [After publishing](/docs/connectors/building/after-publishing): update your server or plugin, and delist
120* [Track published plugin usage](/docs/connectors/building/after-publishing#track-published-plugin-usage): see installs, versions, runs, and error rates on the plugin's **Usage** tab
121* [Manage your directory listing](/docs/connectors/building/managing-your-listing): for an MCP connector, check health and usage metrics and edit the listing
117* [Build your first plugin](/docs/plugins/quickstart.md): build a small example plugin and submit it to the directory
118* [Track your submission](/docs/directory/submission-status.md): check what your submission's status means and who acts next
119* [After publishing](/docs/connectors/building/after-publishing.md): update your server or plugin, and delist
120* [Track published plugin usage](/docs/connectors/building/after-publishing.md#track-published-plugin-usage): see installs, versions, runs, and error rates on the plugin's **Usage** tab
121* [Manage your directory listing](/docs/connectors/building/managing-your-listing.md): for an MCP connector, check health and usage metrics and edit the listing
122122
No line in this hunk matches that.