Manage your listing after publishing changedconnectors/building/after-publishing
Nearest release: v2.1.283, published under an hour after 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 25 Sep 2026 18:00 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 25 Sep 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+54added
Lines−11removed
From line
1
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits5to this page, all time
## Update a published connector or plugin ### MCP server changes ### Plugin changes ### Listing details ## Track published plugin usage ## Directory listing URLs are permanent ## Delist a connector or plugin ## Next steps ## Update your MCP server ## Update your plugin ## Update your listing ## Slugs are permanent ## Delist your connector
The whole hunk
from line 1, old and new numbered
/
from line 1
11# Manage your listing after publishing
22
3> Update your MCP server, plugin, and directory listing after publication
3> Update your MCP server, plugin, and directory listing after publication, keep your listing URL stable, and delist when you need to.
44
5## Update your MCP server
5Once your connector or plugin is listed in the directory, you keep it current from the same developer portal you submitted from, at [claude.ai/directory/manage](https://claude.ai/directory/manage).
66
7An MCP server is a live API. To add, change, or remove tools, deploy the change to your server—no resubmission to Anthropic is required, and there is no scheduled re-review. Claude picks up the new tool surface on the next connection.
7This page is for the developer who owns a published listing.
88
9## Update your plugin
9<Note>
10 If your submission isn't live yet, see [Track your directory submission](/docs/directory/submission-status), which explains what each status in the portal means and who acts next.
11</Note>
1012
11Plugin updates are pushed via your GitHub repo. CI mirrors changes to the public marketplace and runs automated screening on each update.
13You can [update what you've published](#update-a-published-connector-or-plugin), [track how a published plugin is used](#track-published-plugin-usage), [share your listing's permanent URL](#directory-listing-urls-are-permanent), or [delist](#delist-a-connector-or-plugin).
1214
13## Update your listing
15## Update a published connector or plugin
1416
15Edit your description, categories, icon, and other listing metadata from the submissions dashboard at [Organization settings > Directory](https://claude.ai/admin-settings/directory/submissions) in Claude.ai. See [Managing your listing](/docs/connectors/building/managing-your-listing) for what you can edit directly and which changes require review.
17You don't resubmit to Anthropic to change a listed MCP server's tools or a listed plugin's files.
1618
17## Slugs are permanent
19### MCP server changes
1820
21To add, change, or remove tools, deploy the change to your server. The tool names shown on your directory listing are part of the listing details, so update them with a [listing edit](/docs/connectors/building/managing-your-listing#edit-your-listing), which a reviewer approves.
22
23### Plugin changes
24
25To update a listed plugin, push to the branch or tag the directory tracks for it. The directory picks up the new commit, runs the same validation and security scan as your first submission, and shows the result as a new version on the plugin's page in the portal. If you set `version` in `plugin.json`, raise it with each release, because installed copies use it to tell that an update exists.
26
27A version that doesn't pass, or that is held for a reviewer, doesn't take your listing down: the directory keeps serving the last published version until a newer one is published. [Submit a plugin](/docs/plugins/submit#update-a-published-plugin) covers how the directory finds new commits, how to have GitHub notify it on push, and how to change the tracked branch or tag.
28
29### Listing details
30
31For a connector, edit your description, categories, icon, and other listing details from the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage). See [Manage your directory listing](/docs/connectors/building/managing-your-listing) for what you can edit directly and which changes require review.
32
33A plugin listing's name and short description come from `plugin.json` and the README of the version that's live. To change them, edit those files and publish a new version, as [Plugin changes](#plugin-changes) describes. If an Anthropic reviewer edited either field during review, the listing keeps the reviewer's text. From the plugin's **Settings** tab in the developer portal, you can change which surfaces the plugin is listed on, your contact email, and your data handling answers.
34
35## Track published plugin usage
36
37A published plugin's page in the developer portal has a **Usage** tab. The portal is open to the people who [can submit](/docs/directory/publish#confirm-you-can-submit-to-the-directory). Use it to see how many accounts install and use the plugin, which version they're on, and whether the plugin loads and its MCP servers respond without errors.
38
39The **Usage** tab covers a period you choose, up to 90 days, and you can export the figures as CSV. It shows these groups of figures:
40
41* **Reach**: installs, active accounts, and retention, with installs broken out by surface and by where the install came from, such as the **Discover** tab
42* **Versions**: the share of accounts on each version
43* **Components**: how often each skill, command, agent, hook, and MCP server is used
44* **Quality**: load errors by Claude Code version, and tool calls, error rate, and latency for each MCP server
45* **Directory funnel**: listing views, install clicks, and installs
46
47Figures are computed once a day in UTC, and the tab shows the date the data runs through. Until usage is recorded for your plugin, the tab is marked **Preview** and shows sample numbers.
48
49For a connector, [Manage your directory listing](/docs/connectors/building/managing-your-listing#server-health-and-usage-metrics) covers the health badge and usage metrics.
50
51## Directory listing URLs are permanent
52
1953Your directory slug is fixed after publication. It determines your connector's permanent listing URL:
2054
2155```text theme={null}
from line 56
2256https://claude.ai/directory/connectors/SLUG
2357```
2458
25Share this URL from your own documentation or a "Connect to Claude" button to send users directly to your listing. Display names can change via the dashboard; the URL slug cannot.
59Share the listing URL from your own documentation or a **Connect to Claude** button to send users directly to your listing. You can change display names via the dashboard, but you can't change the URL slug.
2660
27## Delist your connector
61## Delist a connector or plugin
2862
29To voluntarily remove your connector from the directory, email `[email protected]`.
63You delist a plugin from the developer portal and a connector by email:
64
65* **To remove a plugin listing:** open the plugin in the developer portal and select **Delist plugin** from the plugin's menu or its **Settings** tab
66* **To bring a plugin listing back:** select **Relist plugin** on the **Settings** tab, which asks the directory to restore the listing
67* **To remove a connector from the directory:** email `[email protected]`
68
69## Next steps
70
71* [Manage your directory listing](/docs/connectors/building/managing-your-listing): for a connector, check submission status and health and usage metrics, and edit the listing
72* [Connector verification](/docs/connectors/verification#list-your-own-connector): see how a listing becomes Verified and what each label means to people installing it
3073
No line in this hunk matches that.