Submit a connector to the directory changedconnectors/building/submission
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 22 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+21added
Lines−21removed
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 remote MCP server or MCP App to the Connectors Directory through the developer portal: requirements, screenshot specs, and what each step asks for.
44
5You submit a remote MCP server to the [Connectors Directory](/docs/connectors/directory) through the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage), where you choose **MCP connector**.
5You submit a remote MCP server to the [Connectors Directory](/docs/connectors/directory.md) through the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage), where you choose **MCP connector**.
66
7This page is for connector authors who are ready to submit. It starts with a [checklist](#pre-submission-checklist-for-connectors), then covers [where to submit your connector](#choose-where-to-submit-your-connector), the [requirements every submission must meet](#meet-the-submission-requirements), and [what to have ready for each step of the portal](#submit-through-the-developer-portal). [Connector review criteria](/docs/connectors/building/review-criteria) explains what reviewers look for in your tools and server, so read it alongside the checklist.
7This page is for connector authors who are ready to submit. It starts with a [checklist](#pre-submission-checklist-for-connectors), then covers [where to submit your connector](#choose-where-to-submit-your-connector), the [requirements every submission must meet](#meet-the-submission-requirements), and [what to have ready for each step of the portal](#submit-through-the-developer-portal). [Connector review criteria](/docs/connectors/building/review-criteria.md) explains what reviewers look for in your tools and server, so read it alongside the checklist.
88
99> [!NOTE]
1010>
11> If you're submitting a plugin rather than a connector, see [Submit a plugin](/docs/plugins/submit) instead.
11> If you're submitting a plugin rather than a connector, see [Submit a plugin](/docs/plugins/submit.md) instead.
1212
1313## Pre-submission checklist for connectors
1414
1515Work through this list before you open the portal. Each item links to where it is explained, and the rest of this page covers the requirements and the portal steps in detail.
1616
17* **Your server is remote and reachable over HTTPS**: the portal asks for an `https://` URL. A local server can't be submitted on its own; include it in a [plugin](/docs/plugins/submit) instead
18* **Authentication works for Claude's client**: OAuth 2.0 if your tools act on a user's account, or no authentication for public data, as [Authentication for connectors](/docs/connectors/building/authentication) describes. You don't need Verified status or any separate approval for authentication to work
19* **Every tool has a `title` and a `readOnlyHint` or `destructiveHint` annotation**: the portal flags tools that are missing them, and [review criteria](/docs/connectors/building/review-criteria#design-tools-that-pass-review) explain how reviewers read tool names and descriptions
20* **You've tested it in Claude**: add the server as a [custom connector](/docs/connectors/building/testing#test-in-claude-as-a-custom-connector) and call each tool from a conversation; the portal's **Test & launch** step asks you to confirm this
21* **You have the listing materials**: documentation URL, privacy policy URL, support contact, an icon, and for an [MCP App](/docs/connectors/building/mcp-apps/getting-started) the [carousel screenshots](#carousel-screenshots-for-mcp-apps)
17* **Your server is remote and reachable over HTTPS**: the portal asks for an `https://` URL. A local server can't be submitted on its own; include it in a [plugin](/docs/plugins/submit.md) instead
18* **Authentication works for Claude's client**: OAuth 2.0 if your tools act on a user's account, or no authentication for public data, as [Authentication for connectors](/docs/connectors/building/authentication.md) describes. You don't need Verified status or any separate approval for authentication to work
19* **Every tool has a `title` and a `readOnlyHint` or `destructiveHint` annotation**: the portal flags tools that are missing them, and [review criteria](/docs/connectors/building/review-criteria.md#design-tools-that-pass-review) explain how reviewers read tool names and descriptions
20* **You've tested it in Claude**: add the server as a [custom connector](/docs/connectors/building/testing.md#test-in-claude-as-a-custom-connector) and call each tool from a conversation; the portal's **Test & launch** step asks you to confirm this
21* **You have the listing materials**: documentation URL, privacy policy URL, support contact, an icon, and for an [MCP App](/docs/connectors/building/mcp-apps/getting-started.md) the [carousel screenshots](#carousel-screenshots-for-mcp-apps)
2222* **You have a test account for reviewers**: credentials for a fully populated account, which you enter in the portal and which only reviewers see
23* **Your account can submit**: any paid Claude plan. See [who can submit](/docs/directory/publish#confirm-you-can-submit-to-the-directory)
24* **If a plugin of yours points at this server, submit the server anyway**: the connector listing gives your organization the server's details, authentication configuration, and dashboard, and lets you pair it with the plugin. See [Submit your plugin, and your MCP server as a connector](/docs/directory/publish#submit-your-plugin-and-your-mcp-server-as-a-connector)
23* **Your account can submit**: any paid Claude plan. See [who can submit](/docs/directory/publish.md#confirm-you-can-submit-to-the-directory)
24* **If a plugin of yours points at this server, submit the server anyway**: the connector listing gives your organization the server's details, authentication configuration, and dashboard, and lets you pair it with the plugin. See [Submit your plugin, and your MCP server as a connector](/docs/directory/publish.md#submit-your-plugin-and-your-mcp-server-as-a-connector)
2525
2626Then open the [developer portal](https://claude.ai/directory/manage), select **Submit new**, and choose **MCP connector**.
2727
from line 30
3030A connector submission is an MCP server, and where you submit it depends on whether the server is remote or local:
3131
3232* **Remote MCP servers**: internet-hosted servers that provide tools and data to Claude. Submit them through the [developer portal](https://claude.ai/directory/manage) and choose **MCP connector**
33* **MCP Apps**: remote MCP servers that [surface interactive UI](/docs/connectors/building/mcp-apps/getting-started). Submit them through the portal as remote servers, and include [carousel screenshots](#carousel-screenshots-for-mcp-apps) for the directory listing
34* **Local MCP servers**: desktop extension listings in the directory are deprecated, and the directory no longer accepts local servers packaged as [MCP Bundles (MCPB)](/docs/connectors/building/mcpb). To distribute a local server through the directory, include it in a [plugin](/docs/plugins/submit)
33* **MCP Apps**: remote MCP servers that [surface interactive UI](/docs/connectors/building/mcp-apps/getting-started.md). Submit them through the portal as remote servers, and include [carousel screenshots](#carousel-screenshots-for-mcp-apps) for the directory listing
34* **Local MCP servers**: desktop extension listings in the directory are deprecated, and the directory no longer accepts local servers packaged as [MCP Bundles (MCPB)](/docs/connectors/building/mcpb.md). To distribute a local server through the directory, include it in a [plugin](/docs/plugins/submit.md)
3535
36Skills aren't a standalone submission type. Bundle them in a [plugin](/docs/plugins/submit).
36Skills aren't a standalone submission type. Bundle them in a [plugin](/docs/plugins/submit.md).
3737
38Anyone on a paid Claude plan can submit through the portal. [Who can submit to the directory](/docs/directory/publish#confirm-you-can-submit-to-the-directory) has the plan, role, and organization requirements, which are the same for connectors and plugins.
38Anyone on a paid Claude plan can submit through the portal. [Who can submit to the directory](/docs/directory/publish.md#confirm-you-can-submit-to-the-directory) has the plan, role, and organization requirements, which are the same for connectors and plugins.
3939
4040## Meet the submission requirements
4141
from line 97
9797* **HTTPS origin**: `https://example.com`. Only the scheme and hostname are matched, and paths, ports, and query strings are ignored. Subdomains aren't implied, so list each one, such as `https://app.example.com` and `https://docs.example.com`
9898* **Custom URI scheme**: `myapp:` for deep links into a native app you own. Only the scheme is matched
9999
100Every origin and scheme you list must be owned by you, the submitting organization. You may not list third-party domains or URI schemes registered to apps you don't publish. Entries you don't own are removed during review. [Open external links from MCP Apps](/docs/connectors/building/mcp-apps/external-links) explains how Claude matches entries and when the prompt still appears.
100Every origin and scheme you list must be owned by you, the submitting organization. You may not list third-party domains or URI schemes registered to apps you don't publish. Entries you don't own are removed during review. [Open external links from MCP Apps](/docs/connectors/building/mcp-apps/external-links.md) explains how Claude matches entries and when the prompt still appears.
101101
102102### Carousel screenshots for MCP Apps
103103
from line 151
151151
152152**6. Authentication**
153153
154How users authenticate: OAuth with dynamic client registration, client ID metadata documents, or Anthropic-held client credentials; a custom connection where users supply their own URL or credentials at connection time; or no authentication. [Authentication](/docs/connectors/building/authentication) covers which modes are supported directly and which need coordination with the review team. If your server starts without authentication and individual tools prompt for it on demand, you can flag that here.
154How users authenticate: OAuth with dynamic client registration, client ID metadata documents, or Anthropic-held client credentials; a custom connection where users supply their own URL or credentials at connection time; or no authentication. [Authentication](/docs/connectors/building/authentication.md) covers which modes are supported directly and which need coordination with the review team. If your server starts without authentication and individual tools prompt for it on demand, you can flag that here.
155155
156156If you chose **URL pattern** in the Connection step, Anthropic-held client credentials can't be used. If you chose **Multiple URLs**, a custom connection can't be used.
157157
from line 173
173173
174174## After you submit
175175
176Anthropic scans your submission automatically for policy compliance and, by default, lists it as a Community connector with no action from you. Some submissions also get a review from a person, and those review times vary with queue volume. The portal is always open for new submissions. Your submission's status and any reviewer feedback appear in the portal at [claude.ai/directory/manage](https://claude.ai/directory/manage), and [Track your directory submission](/docs/directory/submission-status#mcp-connector-statuses) explains what each status in the portal means. [Manage your directory listing](/docs/connectors/building/managing-your-listing) covers reviewer feedback, listing edits, and the server health and usage metrics you get after publication.
176Anthropic scans your submission automatically for policy compliance and, by default, lists it as a Community connector with no action from you. Some submissions also get a review from a person, and those review times vary with queue volume. The portal is always open for new submissions. Your submission's status and any reviewer feedback appear in the portal at [claude.ai/directory/manage](https://claude.ai/directory/manage), and [Track your directory submission](/docs/directory/submission-status.md#mcp-connector-statuses) explains what each status in the portal means. [Manage your directory listing](/docs/connectors/building/managing-your-listing.md) covers reviewer feedback, listing edits, and the server health and usage metrics you get after publication.
177177
179179
180If a submission is stuck, [Contact Anthropic about a submission](/docs/directory/submission-status#contact-anthropic-about-a-submission) gives the channel for an MCP connector.
180If a submission is stuck, [Contact Anthropic about a submission](/docs/directory/submission-status.md#contact-anthropic-about-a-submission) gives the channel for an MCP connector.
181181
182182## Next steps
183183
184* [Manage your directory listing](/docs/connectors/building/managing-your-listing): track review status, respond to reviewer feedback, and edit your listing
185* [After publishing](/docs/connectors/building/after-publishing): release updates to your server, and delist
186* [Connector verification](/docs/connectors/verification#list-your-own-connector): see how a Community listing becomes Verified and what each label means to users
184* [Manage your directory listing](/docs/connectors/building/managing-your-listing.md): track review status, respond to reviewer feedback, and edit your listing
185* [After publishing](/docs/connectors/building/after-publishing.md): release updates to your server, and delist
186* [Connector verification](/docs/connectors/verification.md#list-your-own-connector): see how a Community listing becomes Verified and what each label means to users
187187
No line in this hunk matches that.