Submit your plugin changedplugins/submit
Nearest release: v2.1.283, published 5 hours 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 26 Sep 2026 00:02 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+19added
Lines−19removed
From line
2
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits7to this page, all time
The whole hunk
from line 2, old and new numbered
/
from line 2
22
33> Submit a plugin from a GitHub repository to Anthropic's directory through the developer portal, follow its review, publish it, and release updates.
44
5To list a plugin in [Anthropic's directory](/docs/directory/publish), you submit it from a GitHub repository through the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage). Anthropic checks each version before it can go live, and people can then add the plugin from claude.ai and use it in chat, Cowork, and Claude Code.
5To list a plugin in [Anthropic's directory](/docs/directory/publish.md), you submit it from a GitHub repository through the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage). Anthropic checks each version before it can go live, and people can then add the plugin from claude.ai and use it in chat, Cowork, and Claude Code.
66
7Use this page if your plugin is already in a GitHub repository and you want it listed. If the plugin references a remote MCP server you run, submit that server as an MCP connector too, as [Submit your plugin, and your MCP server as a connector](/docs/directory/publish#submit-your-plugin-and-your-mcp-server-as-a-connector) explains.
7Use this page if your plugin is already in a GitHub repository and you want it listed. If the plugin references a remote MCP server you run, submit that server as an MCP connector too, as [Submit your plugin, and your MCP server as a connector](/docs/directory/publish.md#submit-your-plugin-and-your-mcp-server-as-a-connector) explains.
88
99> [!NOTE]
1010>
11> * To build the plugin first, see [Plugin structure and testing](/docs/plugins/build)
12> * To share it without a public listing, see [Share a plugin with teammates](/docs/plugins/share) or [Roll out a plugin to your whole organization](/docs/plugins/org-rollout)
13> * If you submitted through the earlier Claude Console form, see [Move an earlier submission to the developer portal](/docs/directory/publish#move-an-earlier-submission-to-the-developer-portal)
11> * To build the plugin first, see [Plugin structure and testing](/docs/plugins/build.md)
12> * To share it without a public listing, see [Share a plugin with teammates](/docs/plugins/share.md) or [Roll out a plugin to your whole organization](/docs/plugins/org-rollout.md)
13> * If you submitted through the earlier Claude Console form, see [Move an earlier submission to the developer portal](/docs/directory/publish.md#move-an-earlier-submission-to-the-developer-portal)
1414
1515## Before you submit a plugin
1616
from line 17
1717You need the following to submit from the developer portal on claude.ai:
1818
1919* **A GitHub repository that holds the plugin, and your GitHub account connected on claude.ai.** The directory reads plugins from repositories on github.com. The portal checks that your connected GitHub account can push to the repository, so [connect it first](#connect-your-github-account). The repository can stay private while you validate and submit, and must be public before the listing goes live. See [Submit from a private repository](#submit-from-a-private-repository)
20* **A plan and role that can submit.** See [who can submit to the directory](/docs/directory/publish#confirm-you-can-submit-to-the-directory)
20* **A plan and role that can submit.** See [who can submit to the directory](/docs/directory/publish.md#confirm-you-can-submit-to-the-directory)
2121
2222Every plugin in the directory must comply with the [Anthropic Software Directory Terms](https://support.claude.com/en/articles/13145338-anthropic-software-directory-terms) and the [Anthropic Software Directory Policy](https://support.claude.com/en/articles/13145358-anthropic-software-directory-policy).
2323
24Before you open the portal, work through the [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist). It covers what the directory's checks look for in `plugin.json`, the README, the license, and the rest of the plugin folder. In your terminal, from the folder that contains the plugin folder, run `claude plugin validate ./<plugin-folder>` first to catch formatting and structure problems. The portal's **Validate** step runs more checks than the command does.
24Before you open the portal, work through the [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist.md). It covers what the directory's checks look for in `plugin.json`, the README, the license, and the rest of the plugin folder. In your terminal, from the folder that contains the plugin folder, run `claude plugin validate ./<plugin-folder>` first to catch formatting and structure problems. The portal's **Validate** step runs more checks than the command does.
2525
2626## Submit a plugin
2727
from line 34
3434
3535> [!NOTE]
3636>
37> The other option, **MCP connector**, submits one remote MCP server as its own connector listing. If your plugin references an MCP server you built and you haven't submitted that server yet, submit it separately with **MCP connector** by following [Submit your connector](/docs/connectors/building/submission). [Submit your plugin, and your MCP server as a connector](/docs/directory/publish#submit-your-plugin-and-your-mcp-server-as-a-connector) explains why you submit both.
37> The other option, **MCP connector**, submits one remote MCP server as its own connector listing. If your plugin references an MCP server you built and you haven't submitted that server yet, submit it separately with **MCP connector** by following [Submit your connector](/docs/connectors/building/submission.md). [Submit your plugin, and your MCP server as a connector](/docs/directory/publish.md#submit-your-plugin-and-your-mcp-server-as-a-connector) explains why you submit both.
3838
3939**2. Enter the source and validate**
4040
from line 50
50502. If a finding blocks submission, fix it in the repository and push the fix.
51513. Validate again.
5252
53The [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist) explains what each kind of finding means.
53The [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist.md) explains what each kind of finding means.
5454
5555A validation result applies to one commit. If you push to the branch after validating, validate again before you continue.
5656
from line 87
8787
8888Your organization can have one submission for each repository and folder. To continue an existing submission, open it from **Submissions** in the developer portal instead of creating a second one.
8989
90If another organization has already submitted the same repository and folder, the portal refuses **Submit for review** with **Already submitted by another organization**. If your organization owns the repository, email `[email protected]`. If the earlier submission is one you made through the Claude Console form, see [Move an earlier submission to the developer portal](/docs/directory/publish#move-an-earlier-submission-to-the-developer-portal).
90If another organization has already submitted the same repository and folder, the portal refuses **Submit for review** with **Already submitted by another organization**. If your organization owns the repository, email `[email protected]`. If the earlier submission is one you made through the Claude Console form, see [Move an earlier submission to the developer portal](/docs/directory/publish.md#move-an-earlier-submission-to-the-developer-portal).
9191
9292### Connect your GitHub account
9393
from line 114
114114
115115## After you submit a plugin
116116
117When you select **Submit for review**, the directory scans the newest commit on the tracked branch or tag. Each scan validates the plugin against the directory's rules again and runs a security scan. [Prepare for the security scan](/docs/plugins/pre-submission-checklist#prepare-for-the-security-scan) describes what the security scan looks for.
117When you select **Submit for review**, the directory scans the newest commit on the tracked branch or tag. Each scan validates the plugin against the directory's rules again and runs a security scan. [Prepare for the security scan](/docs/plugins/pre-submission-checklist.md#prepare-for-the-security-scan) describes what the security scan looks for.
118118
119To follow the submission, open the plugin from **Submissions** in the [developer portal](https://claude.ai/directory/manage). The **Versions** tab on the plugin's page lists each scanned commit with the result of its checks. When the newest version isn't live, the plugin's page says why. [Track your directory submission](/docs/directory/submission-status#plugin-bundle-statuses) explains what each status in the portal means and who acts next.
119To follow the submission, open the plugin from **Submissions** in the [developer portal](https://claude.ai/directory/manage). The **Versions** tab on the plugin's page lists each scanned commit with the result of its checks. When the newest version isn't live, the plugin's page says why. [Track your directory submission](/docs/directory/submission-status.md#plugin-bundle-statuses) explains what each status in the portal means and who acts next.
120120
121121A finished scan leaves the version in one of these states:
122122
123123* **Passes every check:** the version can be published, as described in [Publish a passing version](#publish-a-passing-version)
124* **Held for a reviewer:** an Anthropic reviewer reads the version, and it can go live only after the reviewer clears it. The [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist) lists the findings that hold a version
124* **Held for a reviewer:** an Anthropic reviewer reads the version, and it can go live only after the reviewer clears it. The [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist.md) lists the findings that hold a version
125125* **Doesn't pass:** the portal lists the rules that the version breaks. For a failed security scan, the portal shows the category of the finding when the scan recorded one, such as **Sends data to an undisclosed destination**
126126
127127If the directory can't fetch a commit, or a scan ends without a result, the plugin's page says whether the directory retries on its own or whether something in the repository needs fixing. After any fix, select **Check for new commits** on the plugin's page to run the scan again.
from line 148
148148
149149You set auto-publish with the **Auto-publish passing versions** toggle on the **Review and submit** step. After you submit, change it with the **Publish new versions automatically** toggle on the plugin's **Settings** tab. Auto-publish doesn't apply while a reviewer publishes each version.
150150
151If a submission is stuck, [Contact Anthropic about a submission](/docs/directory/submission-status#contact-anthropic-about-a-submission) gives the channel for a plugin.
151If a submission is stuck, [Contact Anthropic about a submission](/docs/directory/submission-status.md#contact-anthropic-about-a-submission) gives the channel for a plugin.
152152
153153## Update a published plugin
154154
from line 185
185185
186186## Next steps
187187
188* [Track your submission](/docs/directory/submission-status#plugin-bundle-statuses): check what the status next to your plugin's name means and who acts next
189* [Plugin pre-submission checklist](/docs/plugins/pre-submission-checklist): fix each validation and scan finding
190* [After publishing](/docs/connectors/building/after-publishing): update your plugin and listing, and delist
191* [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
192* [Manage your directory listing](/docs/connectors/building/managing-your-listing): for an MCP connector, check health and usage metrics and edit the listing
188* [Track your submission](/docs/directory/submission-status.md#plugin-bundle-statuses): check what the status next to your plugin's name means and who acts next
189* [Plugin pre-submission checklist](/docs/plugins/pre-submission-checklist.md): fix each validation and scan finding
190* [After publishing](/docs/connectors/building/after-publishing.md): update your plugin and listing, and delist
191* [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
192* [Manage your directory listing](/docs/connectors/building/managing-your-listing.md): for an MCP connector, check health and usage metrics and edit the listing
193193
No line in this hunk matches that.