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 20 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+43added
Lines−45removed
From line
6
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits6to this page, all time
The whole hunk
from line 6, old and new numbered
/
from line 6
66
77Use 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.
88
9<Note>
10 * To build the plugin first, see [Plugin structure and testing](/docs/plugins/build)
11 * 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)
12 * 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)
13</Note>
9> [!NOTE]
10>
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)
1414
1515## Before you submit a plugin
1616
from line 27
2727
2828Each plugin folder is its own submission in the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage), so a repository that holds several plugins needs one submission for each.
2929
30<Steps>
31 <Step title="Open the portal">
32 1. Open the [developer portal](https://claude.ai/directory/manage) and select **Submit new**.
33 2. When the portal asks **What would you like to submit?**, select **Plugin bundle**.
30**1. Open the portal**
3431
35 <Note>
36 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 </Note>
38 </Step>
321. Open the [developer portal](https://claude.ai/directory/manage) and select **Submit new**.
332. When the portal asks **What would you like to submit?**, select **Plugin bundle**.
3934
40 <Step title="Enter the source and validate">
41 On the **Source** step, fill in the fields:
35> [!NOTE]
36>
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.
4238
43 * **Repository**: the GitHub repository's URL, or `owner/repo`. If you paste a link to a folder on a branch, the portal fills in the path and branch for you
44 * **Plugin path (optional)**: the folder that holds `.claude-plugin/plugin.json`, if the plugin isn't at the repository root
45 * **Branch or tag (optional)**: the branch or tag that the directory follows for new versions. The portal calls this the tracked branch or tag. Leave the field empty to follow the repository's default branch. A tag stays on its commit until you change the tag. If the branch name contains a slash, type the name in this field or enter `owner/repo@branch` in **Repository**, instead of pasting a folder link
39**2. Enter the source and validate**
4640
47 Then validate the plugin:
41On the **Source** step, fill in the fields:
4842
49 1. Select **Validate** to run the directory's validation checks on the plugin.
50 2. If a finding blocks submission, fix it in the repository and push the fix.
51 3. Validate again.
43* **Repository**: the GitHub repository's URL, or `owner/repo`. If you paste a link to a folder on a branch, the portal fills in the path and branch for you
44* **Plugin path (optional)**: the folder that holds `.claude-plugin/plugin.json`, if the plugin isn't at the repository root
45* **Branch or tag (optional)**: the branch or tag that the directory follows for new versions. The portal calls this the tracked branch or tag. Leave the field empty to follow the repository's default branch. A tag stays on its commit until you change the tag. If the branch name contains a slash, type the name in this field or enter `owner/repo@branch` in **Repository**, instead of pasting a folder link
5246
53 The [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist) explains what each kind of finding means.
47Then validate the plugin:
5448
55 A validation result applies to one commit. If you push to the branch after validating, validate again before you continue.
56 </Step>
491. Select **Validate** to run the directory's validation checks on the plugin.
502. If a finding blocks submission, fix it in the repository and push the fix.
513. Validate again.
5752
58 <Step title="Check the listing details">
59 The **Listing details** step shows how the plugin appears in the directory, read from `plugin.json` and the README. To change a field before you submit, edit `plugin.json` or the README in the repository and validate again. Once the plugin is listed, its name and short description follow the version that's live, so to change them later, edit `plugin.json` or the README and publish a new version.
60 </Step>
53The [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist) explains what each kind of finding means.
6154
62 <Step title="Answer the data handling questions">
63 On the **Data handling** step, answer each question: whether the plugin reads or stores personal data, whether it sends data to services other than its declared connectors, how long it keeps data, and whether it's intended for people under 18.
64 </Step>
55A validation result applies to one commit. If you push to the branch after validating, validate again before you continue.
6556
66 <Step title="Complete the compliance step">
67 On the **Compliance** step, check the contact email and select the acknowledgements:
57**3. Check the listing details**
6858
69 1. Check that the contact email is an address where Anthropic can reach you about the submission.
70 2. Select all four acknowledgements.
71 </Step>
59The **Listing details** step shows how the plugin appears in the directory, read from `plugin.json` and the README. To change a field before you submit, edit `plugin.json` or the README in the repository and validate again. Once the plugin is listed, its name and short description follow the version that's live, so to change them later, edit `plugin.json` or the README and publish a new version.
7260
73 <Step title="Review and submit">
74 On the **Review and submit** step, confirm the details, choose how new versions arrive, and submit:
61**4. Answer the data handling questions**
7562
76 1. Confirm the details.
77 2. Under **How new versions reach the directory**, choose **GitHub push webhook**, which is selected by default, or **Scheduled check only**. With either option, the directory also checks the tracked branch or tag for new commits on a schedule.
78 3. Select **Submit for review**.
63On the **Data handling** step, answer each question: whether the plugin reads or stores personal data, whether it sends data to services other than its declared connectors, how long it keeps data, and whether it's intended for people under 18.
7964
80 If you kept **GitHub push webhook**, the **Plugin submitted for review** page offers **Set up push updates**. You need admin access to the repository on GitHub to set up the webhook.
65**5. Complete the compliance step**
8166
82 To set it up later, open the plugin from **Submissions** in the developer portal and select **Set up** under **Updates** on the **Settings** tab.
83 </Step>
84</Steps>
67On the **Compliance** step, check the contact email and select the acknowledgements:
68
691. Check that the contact email is an address where Anthropic can reach you about the submission.
702. Select all four acknowledgements.
71
72**6. Review and submit**
73
74On the **Review and submit** step, confirm the details, choose how new versions arrive, and submit:
75
761. Confirm the details.
772. Under **How new versions reach the directory**, choose **GitHub push webhook**, which is selected by default, or **Scheduled check only**. With either option, the directory also checks the tracked branch or tag for new commits on a schedule.
783. Select **Submit for review**.
79
80If you kept **GitHub push webhook**, the **Plugin submitted for review** page offers **Set up push updates**. You need admin access to the repository on GitHub to set up the webhook.
81
82To set it up later, open the plugin from **Submissions** in the developer portal and select **Set up** under **Updates** on the **Settings** tab.
8583
8684### Submission limits and duplicates
8785
No line in this hunk matches that.