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 25 Sep 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+92added
Lines−78removed
From line
1
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits4to this page, all time
# Submit a connector to the directory ## Pre-submission checklist for connectors ## Choose where to submit your connector ## Meet the submission requirements ### Directory terms ### Requirements for every connector ### Privacy policy for local connectors ### Allowed link URIs ### Carousel screenshots for MCP Apps ## Submit through the developer portal ## After you submit ## Next steps # Submitting to the Connectors Directory ## What you can submit ## Before you start ## Directory terms & conditions ## Submission requirements ## Privacy policy requirements ## Allowed link URIs ## Asset specifications ### Carousel screenshots (MCP Apps) ## Review process ## Submit your connector ### What to expect in the portal
The whole hunk
from line 1, old and new numbered
/
from line 1
1# Submitting to the Connectors Directory
1# Submit a connector to the directory
22
3> Submit your MCP connector to the Connectors Directory
3> 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
5The [Connectors Directory](/docs/connectors/directory) aims to be a collection of high-quality, vetted, and reviewed MCP servers that are helpful and harmless to users. Anyone is welcome to build MCP servers, but only servers meeting the review standards outlined on this page will be included in the directory.
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**.
66
7## What you can submit
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.
88
9Developers can submit:
9<Note>
10 If you're submitting a plugin rather than a connector, see [Submit a plugin](/docs/plugins/submit) instead.
11</Note>
1012
11* **Remote MCP servers** — internet-hosted servers that provide tools and data to Claude
12* **Desktop extensions** — local MCP servers packaged as [MCP Bundles (MCPB)](https://github.com/modelcontextprotocol/mcpb) for Claude Desktop
13* **[MCP Apps](/docs/connectors/building/mcp-apps/getting-started)** — MCP servers that surface interactive UI elements. These have the additional requirement of including screenshots for submission and listing in the directory.
13## Pre-submission checklist for connectors
1414
15## Before you start
15Work 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
17Remote MCP server submissions happen inside Claude.ai, in the [submission portal](https://claude.ai/admin-settings/directory/submissions/new). The portal is part of your organization's settings, so you need:
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)
22* **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)
1825
19* **A Team or Enterprise organization.** Organization settings aren't available on individual plans.
20* **Directory management access.** By default, only organization Owners and Primary owners can submit and manage directory listings. On Enterprise, an Owner can delegate this to other members by creating a custom role in **Organization settings > Roles** with either the **Directory** permission (directory submissions only) or the **Libraries** permission (broader: it also covers managing the organization's plugins, connectors, and skills), and assigning that role. Team plans don't have custom roles, so on Team this stays with Owners.
26Then open the [developer portal](https://claude.ai/directory/manage), select **Submit new**, and choose **MCP connector**.
2127
22Desktop extensions (MCPB) use a separate [submission form](https://clau.de/desktop-extention-submission) and don't require the portal.
28## Choose where to submit your connector
2329
24## Directory terms & conditions
30A connector submission is an MCP server, and where you submit it depends on whether the server is remote or local:
2531
32* **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)
35
36Skills aren't a standalone submission type. Bundle them in a [plugin](/docs/plugins/submit).
37
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.
39
40## Meet the submission requirements
41
42Every connector in the directory must comply with the directory terms and meet a fixed set of security, annotation, authentication, privacy, and documentation requirements. MCP Apps add screenshot requirements, and connectors that open external links can add an allowlist.
43
44### Directory terms
45
2646All servers in the directory must comply with:
2747
2848* [Anthropic Software Directory Terms](https://support.claude.com/en/articles/13145338-anthropic-software-directory-terms)
from line 54
3454* Respond to security issues promptly
3555* Provide accurate descriptions and documentation
3656
37## Submission requirements
57### Requirements for every connector
3858
39All MCP connectors submitted to the directory must meet:
59All MCP connectors submitted to the directory must meet these requirements:
4060
411. **Security**: Meet Anthropic's security standards
422. **Tool annotations**: All tools must include a `title` and the applicable `readOnlyHint` or `destructiveHint`
433. **Authentication**: Use OAuth 2.0 for authenticated services
444. **Privacy Policy**: Local connectors must include privacy policies
455. **Documentation**: Provide clear setup and usage instructions
61* **Security**: meet Anthropic's security standards
62* **Tool annotations**: every tool includes a `title` and the applicable `readOnlyHint` or `destructiveHint`
63* **Authentication**: use OAuth 2.0 for authenticated services
64* **Privacy policy**: local connectors must include privacy policies
65* **Documentation**: provide clear setup and usage instructions
4666
4767If your connector opens external links, also provide your [allowed link URIs](#allowed-link-uris) so users aren't prompted to confirm each one.
4868
49## Privacy policy requirements
69### Privacy policy for local connectors
5070
5171Local connectors must include:
5272
531. "Privacy Policy" section in README.md
542. `privacy_policies` array in manifest.json (manifest\_version 0.2+)
553. HTTPS URLs to privacy policies
73* A "Privacy Policy" section in `README.md`
74* A `privacy_policies` array in `manifest.json`, for `manifest_version` 0.2 and later
75* HTTPS URLs to privacy policies
5676
5777The privacy policy must cover:
5878
from line 86
6686 Missing or incomplete privacy policies result in immediate rejection.
6787</Warning>
6888
69## Allowed link URIs
89### Allowed link URIs
7090
71If your connector uses the `ui/open-link` capability to open URLs in the user's browser or native apps, provide the list of link targets your server will request. Claude uses this list to suppress the "Open external link" confirmation prompt for destinations you've declared. Links to any other destination still work—users are simply asked to confirm before the link opens.
91If your connector uses the `ui/open-link` capability to open URLs in the user's browser or native apps, provide the list of link targets your server will request. Claude uses this list to suppress the **Open external link** confirmation prompt for destinations you've declared. Links to any other destination still work, but users are asked to confirm before the link opens.
7292
73Provide each entry in one of two forms:
93The allowed link URIs list is optional. If you omit it, your connector functions normally, and users see a confirmation prompt each time it opens a link.
7494
75* **HTTPS origin** — `https://example.com`. Only the scheme and hostname are matched; paths, ports, and query strings are ignored. Subdomains are not implied—list each one (`https://app.example.com`, `https://docs.example.com`).
76* **Custom URI scheme** — `myapp:` for deep links into a native app you own (for example, `spotify:` or `notion:`). Only the scheme is matched.
95Provide each entry in one of these forms:
7796
78Every 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 will be removed during review.
97* **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`
98* **Custom URI scheme**: `myapp:` for deep links into a native app you own. Only the scheme is matched
7999
80<Note>
81 This field is optional. If omitted, your connector functions normally, but users are shown a confirmation prompt each time it opens a link.
82</Note>
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.
83101
84## Asset specifications
102### Carousel screenshots for MCP Apps
85103
86### Carousel screenshots (MCP Apps)
104An MCP App submission includes screenshots for its directory listing carousel. Prepare them to these specifications:
87105
88* **Format:** PNG
89* **Width:** at least 1000px
90* **Count:** 3–5 images
91* **Crop:** to the app response only—**do not include the prompt** in the image
92* **Aspect ratio:** any
93* **Paired prompts:** provide the prompt text separately for each screenshot
94* **Mobile:** no separate mobile assets are required—one batch covers all surfaces
95* **Video/GIF:** not accepted
106* **Format**: PNG
107* **Width**: at least 1000px
108* **Count**: 3–5 images
109* **Crop**: to the app response only, without the prompt in the image
110* **Aspect ratio**: any
111* **Paired prompts**: provide the prompt text separately for each screenshot
112* **Mobile**: no separate mobile assets are required, and one batch covers all surfaces
113* **Video or GIF**: not accepted
96114
97115A carousel template is available in the [Anthropic MCP Apps Figma community file](https://www.figma.com/community/file/1597641111449594397/mcp-apps-for-claude).
98116
99117### Detail card description
100118
101You write the detail card description in the submission portal. It is not editable by Anthropic. The disclaimer text shown on connector cards is general and not customizable per partner.
119You write the detail card description in the submission portal, and Anthropic can't edit it. The disclaimer text shown on connector cards is general and not customizable per partner.
102120
103## Review process
121## Submit through the developer portal
104122
105Review times vary with queue volume. The submission portal is always open.
123The developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage) takes your submission in a series of steps. Before you open it, have these ready:
106124
107After you submit, track your submission's status and read reviewer feedback in the [submissions dashboard](https://claude.ai/admin-settings/directory/submissions). See [Managing your listing](/docs/connectors/building/managing-your-listing) for what's available there, including server health and usage metrics after publication. Email `[email protected]` for escalations.
125* Your documentation URL and privacy policy URL
126* Your connector's icon
127* Test account credentials for reviewers
128* Carousel screenshots, if you're submitting an MCP App, per the [screenshot specifications](#carousel-screenshots-for-mcp-apps)
108129
109Run the [pre-submission checklist](/docs/connectors/building/review-criteria) and, for plugins, `claude plugin validate` before you submit.
130Your progress saves automatically in your browser as you move between steps, so within a browser session you can return to earlier steps without losing work. Each step asks for the following:
110131
111## Submit your connector
112
113Ready to submit? Use the path that matches your connector type:
114
115* **Remote MCP servers (including MCP Apps)**: submit through the [submission portal](https://claude.ai/admin-settings/directory/submissions/new) in your organization's settings on Claude.ai. See [Before you start](#before-you-start) for access requirements.
116* **Desktop extensions (MCPB)**: use the [desktop extension submission form](https://clau.de/desktop-extention-submission).
117
118Skills are not a standalone submission type—bundle them in a [plugin](/docs/plugins/submit).
119
120### What to expect in the portal
121
122Before you start, have your documentation URL, privacy policy URL, icon, and test account credentials ready, plus carousel screenshots if you're submitting an MCP App (see [asset specifications](#asset-specifications) above).
123
124The portal walks you through the following steps. Your progress saves automatically in your browser as you move between steps, so within a browser session you can jump back to earlier steps without losing work.
125
126132<Steps>
127 <Step title="Introduction">
128 Explains what a directory listing does and doesn't do: inclusion makes your connector discoverable but doesn't change the tools it exposes. The portal accepts remote MCP servers only. Local servers are distributed as [desktop extensions](https://clau.de/desktop-extention-submission) or [plugins](/docs/plugins/submit) instead.
129 </Step>
130
131133 <Step title="Connection">
132 Connect the server you're submitting. You confirm the server URL (must be `https://`), the transport (streamable HTTP or SSE), and how users reach your server: one **Universal URL** for everyone, a fixed list of **Multiple URLs**, or a **URL pattern** that each user's own URL must match. See [Servers with per-customer URLs](/docs/connectors/building/authentication#servers-with-per-customer-urls) for how this choice limits your authentication options.
134 Connect the server you're submitting, by pasting its `https://` URL or choosing a custom connector you've already added to Claude. If your users connect to different URLs, select **Users connect to different URLs** and choose **Multiple URLs** or **URL pattern**.
133135 </Step>
134136
135137 <Step title="Tools">
136 Your server's tools, prompts, and resources sync automatically from the connected server, grouped by whether their annotations declare them read-only or write (tools without annotations are grouped separately). If any tools are flagged for missing titles or annotations, fix them on your server before submitting.
138 Your server's tools, prompts, and resources sync automatically from the connected server, grouped by whether their annotations declare them read-only or write. If any tools are flagged for missing titles or annotations, fix them on your server before submitting.
137139 </Step>
138140
139141 <Step title="Listing">
140 The public-facing listing: server name (100 characters max), tagline (55 characters max), description (2,000 characters max), one to five categories, documentation URL, privacy policy URL, support contact, icon, and the URL slug for your listing page. The slug is permanent once published.
142 The public-facing listing: server name up to 100 characters, one-liner up to 200 characters, description up to 2,000 characters, one to five categories, documentation URL, privacy policy URL, support contact, icon, and the URL slug for your listing page. The slug is permanent once published.
141143 </Step>
142144
143145 <Step title="Use cases">
144 Describe the primary use cases, what users need before they can connect (accounts, plans, or other setup), and whether the connector reads data, writes data, or both.
146 The primary use cases, what users need before they can connect, such as accounts, plans, or other setup, and whether the connector reads data, writes data, or both.
145147 </Step>
146148
147149 <Step title="Company">
148 Company name and website, plus a primary contact for review updates. The contact name and email are pre-filled from your account.
150 Company name and website, plus a primary contact for review updates.
149151 </Step>
150152
151153 <Step title="Authentication">
152 How 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. See [authentication](/docs/connectors/building/authentication) for which modes are supported out of the box 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.
154 How 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.
153155
154156 If 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.
155157 </Step>
from line 161
159161 </Step>
160162
161163 <Step title="Test & launch">
162 Test-account setup and access instructions detailed enough for a reviewer to access your server end to end: every link, credential, and step, including credentials for a fully populated account where relevant. You also confirm you've run every tool yourself, either via MCP Inspector or as a custom connector in Claude.
164 Test-account setup and access instructions detailed enough for a reviewer to connect to your server and run its tools: every link, credential, and step, including credentials for a fully populated account where relevant. You also confirm you've run every tool yourself, either through MCP Inspector or as a custom connector in Claude.
163165 </Step>
164166
165167 <Step title="Compliance">
from line 168
166168 Seven policy acknowledgments covering the directory guidelines, first-party API usage, financial transactions, AI media generation, prompt injection, conversation data collection, and public documentation. All seven are required.
167169 </Step>
168170
169 <Step title="Review">
170 A final read-through of everything you've entered. Any quality warnings (for example, very short answers) are shown here and shared with the review team alongside your submission. Submit when you're ready.
171 <Step title="Review and submit">
172 Everything you've entered, for a final check before you submit. Any quality warnings, such as very short answers, appear here and are shared with the review team alongside your submission.
171173 </Step>
172174</Steps>
173175
174After you submit, your submission's status and any reviewer feedback appear in the [submissions dashboard](https://claude.ai/admin-settings/directory/submissions). See [Managing your listing](/docs/connectors/building/managing-your-listing).
176## After you submit
177
178Anthropic 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.
179
180For escalations, email `[email protected]`.
181
182If 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.
183
184## Next steps
185
186* [Manage your directory listing](/docs/connectors/building/managing-your-listing): track review status, respond to reviewer feedback, and edit your listing
187* [After publishing](/docs/connectors/building/after-publishing): release updates to your server, and delist
188* [Connector verification](/docs/connectors/verification#list-your-own-connector): see how a Community listing becomes Verified and what each label means to users
175189
No line in this hunk matches that.