One read of Claude Documentationclaude-docs-20261002T200707Z
4 pages moved out of 260 read.
Pages moved
4
significant first
Pages read
260
in this capture
Captured
20:07 UTC
Corpus hash
201773bedaf4
corpus-hash
What this read moved
1-4 of 4claude-tag/users/models Changed · +4 / -2 lines
from line 24
2424
2525The same request works in a one-to-one direct message, where it applies to that conversation only. In a group DM, the switch applies to the thread you ask in.
2626
27You can name a model family instead of a version, for example "use the latest Opus here". Claude switches to the newest model of that family your organization offers.
28
2729## Set a default model for the channel
2830
2931To change what new threads in a channel start on, ask for the channel, not just the thread.
from line 34
3234@Claude use Sonnet for this thread, and make it the default model for this channel.
3335```
3436
35Claude sets the channel's default model. New threads in the channel start on it. A thread already underway switches to it at the next message anyone posts there, unless someone in that thread has already had Claude switch models. If an admin has set the scope's **Channel member edits** setting to **Block**, Claude declines to set the channel default; ask for the thread alone instead.
37Claude sets the channel's default model. New threads in the channel start on it. If you asked for a family rather than a version, the default keeps following that family: when your organization gets a newer model in it, new threads start on the newer model without anyone changing the setting. A thread already underway switches to it at the next message anyone posts there, unless someone in that thread has already had Claude switch models. If an admin has set the scope's **Channel member edits** setting to **Block**, Claude declines to set the channel default; ask for the thread alone instead.
3638
3739Admins set the same default from claude.ai, per workspace or channel; see [choose the model for a scope](/docs/claude-tag/admins/customize#choose-the-model-for-a-scope).
3840
3941## Choose the model for your direct messages
4042
41Open the Claude app's **Home** tab in Slack. When model selection is enabled for your organization, the tab includes a model selector for one-to-one direct messages. New direct message conversations you start with Claude use the model you pick there. The selector offers only the models your organization allows.
43Open the Claude app's **Home** tab in Slack. When model selection is enabled for your organization, the tab includes a model selector for one-to-one direct messages. New direct message conversations you start with Claude use the model you pick there. The selector offers only the models your organization allows, and lists each model family as an option such as **Opus (latest)** ahead of the specific versions; with a family option, each new direct message conversation starts on the newest model of that family.
4244
4345The selector doesn't change a conversation already underway. To change one of those, ask Claude to switch in that conversation.
4446
directory/publish Changed · +64 / -61 lines
## Submit your plugin, and your MCP server as a connector ## Prepare for review ## Move an earlier submission to the developer portal ## What a listing gets you ### Submit your plugin, and your MCP server as a connector ### What a listing gets you ### Move an earlier submission to the developer portal ### Prepare for review
from line 2
22
33> Submit a plugin or MCP connector to Anthropic's directory: the two submission kinds, who can submit, what review involves, and where to start.
44
5The directory is Anthropic's catalog of plugins and connectors that people browse inside Claude, on the [**Customize**](https://claude.ai/customize) page in claude.ai and the desktop app. A listing reaches people 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.
5The [directory](https://claude.ai/directory) is Anthropic's catalog of plugins and connectors that people browse inside Claude.
66
77This page is for developers who have built a plugin, or the MCP server behind one, and want it listed. Anyone on a paid Claude plan can submit, there's no partner program to apply to first, and Anthropic checks each submission before it's listed.
88
9If you're ready to submit, open the [developer portal](https://claude.ai/directory/manage) or jump to [Start a submission in the developer portal](#start-a-submission-in-the-developer-portal).
10
911<Note>
1012 * If you're still deciding what goes in your plugin, see [Decide what to include in your plugin](/docs/connectors/building/what-to-build)
1113 * If you want to build a small example plugin and submit it, see [Build your first plugin](/docs/plugins/quickstart)
from line 15
1315 * 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
1416</Note>
1517
16If you're ready to submit, open the [developer portal](https://claude.ai/directory/manage) or jump to [Start a submission in the developer portal](#start-a-submission-in-the-developer-portal).
17
1818## Before you submit to the directory
1919
2020A directory listing is either a plugin bundle or an MCP connector.
2121
22### Submit your plugin, and your MCP server as a connector
22* If you have a remote MCP server, see [Submit your plugin, and your MCP server as a connector](#submit-your-plugin-and-your-mcp-server-as-a-connector)
23* If you submitted through the earlier Claude Console form, see [Move an earlier submission to the developer portal](#move-an-earlier-submission-to-the-developer-portal)
2324
25### Confirm you can submit to the directory
26
27You submit from a claude.ai account, and the listing belongs to the organization you submit from. Before you start, confirm each of these:
28
29* **Plan**: Pro, Max, Team, or Enterprise. Free accounts can't submit
30* **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**](https://claude.ai/admin-settings/roles). If you don't have one of those roles, ask an Owner
31* **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
32
33## Start a submission in the developer portal
34
35You submit and maintain listings in the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage).
36
37To start a submission:
38
39<Steps>
40 <Step title="Select Submit new">
41 In the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage), select **Submit new**.
42 </Step>
43
44 <Step title="Choose the submission type">
45 Under **What would you like to submit?**, choose **Plugin bundle** or **MCP connector**.
46 </Step>
47
48 <Step title="Follow the checklist and submit pages">
49 Work through the checklist and submit pages for that kind:
50
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
53 </Step>
54</Steps>
55
56## Submit your plugin, and your MCP server as a connector
57
2458A 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:
2559
2660| | Plugin bundle | MCP connector |
from line 75
4175
4276Skills aren't a submission type on their own. Put them in a bundle.
4377
44### What a listing gets you
78## Prepare for review
4579
46A directory listing gives you:
80Anthropic checks every submission before it's listed, and checks a plugin bundle again with each new version.
4781
48* **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
49* **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
50* **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
51* **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
82* **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
83* **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)
5284
53### Confirm you can submit to the directory
85Every 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).
5486
55You submit from a claude.ai account, and the listing belongs to the organization you submit from. Before you start, confirm each of these:
87There'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.
5688
57* **Plan**: Pro, Max, Team, or Enterprise. Free accounts can't submit
58* **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**](https://claude.ai/admin-settings/roles). If you don't have one of those roles, ask an Owner
59* **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
89Review 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.
6090
61### Move an earlier submission to the developer portal
91## Move an earlier submission to the developer portal
6292
6393A listing you submitted before the developer portal existed stays as it is. Move it to the portal to get what the portal adds:
6494
from line 103
73103
74104Until 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**.
75105
76### Prepare for review
106## What a listing gets you
77107
78Anthropic checks every submission before it's listed, and checks a plugin bundle again with each new version.
108A directory listing gives you:
79109
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)
82
83Every 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).
84
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.
86
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.
88
89## Start a submission in the developer portal
90
91You submit and maintain listings in the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage).
92
93To start a submission:
94
95<Steps>
96 <Step title="Select Submit new">
97 In the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage), select **Submit new**.
98 </Step>
99
100 <Step title="Choose the submission type">
101 Under **What would you like to submit?**, choose **Plugin bundle** or **MCP connector**.
102 </Step>
103
104 <Step title="Follow the checklist and submit pages">
105 Work through the checklist and submit pages for that kind:
106
107 * [Plugin pre-submission checklist](/docs/plugins/pre-submission-checklist), then [Submit a plugin](/docs/plugins/submit): for a plugin bundle
108 * [Connector pre-submission checklist](/docs/connectors/building/review-criteria), then [Submit a connector](/docs/connectors/building/submission): for an MCP connector
109 </Step>
110</Steps>
110* **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)
111* **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
112* **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
113* **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
111114
112115## Next steps
113116
claude-tag/admins/customize Changed · +1 / -1 lines
from line 62
6262
6363## Choose the model for a scope
6464
65Each scope carries a **Default model** setting in its **Advanced** section, alongside the [environment](/docs/claude-tag/concepts/glossary#environment) and guest controls. It sets the model new channel sessions in that scope start on. The options are the models your organization allows, such as Opus and Sonnet models, regardless of any individual member's own model access. A scope without its own setting inherits from its parent, and a channel's setting overrides its workspace's. The **Inherit** option shows which model the scope resolves to.
65Each scope carries a **Default model** setting in its **Advanced** section, alongside the [environment](/docs/claude-tag/concepts/glossary#environment) and guest controls. It sets the model new channel sessions in that scope start on. The options are the models your organization allows, such as Opus and Sonnet models, regardless of any individual member's own model access. The picker also lists model families. A scope set to a family option starts sessions on the newest model of that family your organization allows, and moves to a newer one when your organization gets it, without you changing the setting. A scope without its own setting inherits from its parent, and a channel's setting overrides its workspace's. The **Inherit** option shows which model the scope resolves to.
6666
6767To keep sessions on a model you chose, set a specific model at the organization scope rather than leaving the setting unset; every scope without an override then follows it.
6868
plugins/platform-support Changed · +1 / -1 lines
from line 49
4949| Hosts for a marketplace you add yourself | GitHub and GitHub Enterprise repositories, and public GitLab and Bitbucket repositories | Any Git repository, GitHub shorthand, URL, or local path | Repositories your organization syncs to distribute plugins follow [different rules](/docs/plugins/org-sync#plugin-sources-that-organization-sync-accepts) |
5050| Marketplace and plugin limits | Up to 25 marketplaces that you add yourself, counted for your account in each organization. Each plugin can contain up to 5,000 files and 200 MB, and 200 MB is also the largest file that **Upload plugin** accepts. | No account limits apply; installs are per machine | |
5151| Install from a file | **Add > Upload plugin** with a zip of the folder | `claude --plugin-dir <path>` for one session | [Plugin structure and testing](/docs/plugins/build#test-the-plugin-on-each-surface) |
52| Browse the directory | **Discover** in **Customize > Plugins**, on Pro, Max, Team, and Enterprise plans. On Team and Enterprise plans, an Owner can [remove the directory as a source](/docs/plugins/admin#manage-synced-marketplaces) for the organization. | Not in `/plugin`; a plugin added from the directory on claude.ai reaches Claude Code as a synced plugin | [Publish to the directory](/docs/directory/publish) |
52| Browse the directory | **Discover** in **Customize > Plugins**, on Pro, Max, Team, and Enterprise plans. On Team and Enterprise plans, an Owner can [remove the directory as a source](/docs/plugins/admin#manage-synced-marketplaces) for the organization. | `/plugin directory`, in Claude Code v2.1.287 and later. A plugin added from the directory on claude.ai also reaches Claude Code as a synced plugin. | [Publish to the directory](/docs/directory/publish) |
5353| Organization controls | An Owner sets each plugin to **Not available**, **Available to install**, **Installed by default**, or **Required** | In managed settings, an admin allowlists or blocks marketplaces and force-installs plugins | [Manage plugins for your organization](/docs/plugins/admin), and the [Claude Code equivalent](https://code.claude.com/docs/en/plugins/org) |
5454
5555## Related resources