Connectors directory changedconnectors/directory
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+42added
Lines−30removed
From line
1
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits3to this page, all time
## Understand how the directory works ## Browse the directory ## Request a connector on a Team plan ## Recognize when a connector's endpoint changes ## Submit to the directory ## Next steps ## How the directory works ## Browsing the directory ## Requesting a connector on a Team plan ## When a connector's endpoint changes ## Submitting to the directory ## Related topics
The whole hunk
from line 1, old and new numbered
/
from line 1
11# Connectors directory
22
3> Browse verified and community MCP integrations for Claude
3> Browse verified and community MCP connectors in the Connectors Directory, one catalog for claude.ai, Claude Desktop, mobile, Claude Code, and Cowork
44
5The Connectors Directory is a catalog of [MCP](/docs/connectors/building/mcp) servers that work across all Claude products — Claude.ai, Claude Desktop, Claude Mobile, Claude Code, and Cowork.
5The Connectors Directory is a catalog of [MCP](/docs/connectors/building/mcp) servers that work across all Claude products: claude.ai, Claude Desktop, Claude Mobile, Claude Code, and Cowork.
66
7The directory contains both verified connectors and community connectors. Verified connectors have been tested by Anthropic for quality and compatibility and met the Software Directory Policy requirements at the time of review, though verification is not a security audit. Anthropic screens community connectors before listing but does not review them in depth. The label reflects the level of review each connector received, not how it works: once connected, a community connector has the same capabilities and access as any connector you grant. See [connector verification](/docs/connectors/verification) to learn what each label means.
7The directory contains both verified connectors and community connectors. Verification isn't a security audit. [Connector verification](/docs/connectors/verification) explains what each label means.
88
99<Note>
1010 All connectors in the directory are subject to the [Anthropic Software Directory Policy](https://support.claude.com/en/articles/13145358-anthropic-software-directory-policy) and the [Anthropic Software Directory Terms](https://support.claude.com/en/articles/13145338-anthropic-software-directory-terms).
1111</Note>
1212
13## How the directory works
13## Understand how the directory works
1414
15* The same catalog serves Claude.ai, Cowork, Desktop, mobile, and Claude Code.
16* Directory connectors are eligible for **Suggested Connectors**—in-chat recommendations when relevant to the user's task. Every directory entry is included automatically.
17* Ranking is usage-based, similar to other app stores.
18* No domain-ownership proof (DNS or `.well-known`) is required—that requirement applies only to the open MCP Registry, not the Anthropic Directory.
19* The help-docs link shown in the in-product connector setup flow is not partner-customizable.
15* The same catalog serves claude.ai, Cowork, Desktop, mobile, and Claude Code
16* Directory connectors are eligible for **Suggested Connectors**, which are in-chat recommendations shown when relevant to the user's task. Every directory entry is included automatically
17* Ranking is usage-based, similar to other app stores
18* No domain-ownership proof (DNS or `.well-known`) is required. That requirement applies only to the open MCP Registry, not the Anthropic Directory
19* The help-docs link shown in the in-product connector setup flow is not partner-customizable
2020
21Directory connectors and custom connectors run on the same infrastructure—see [directory vs custom](/docs/connectors/building/directory-vs-custom).
21Directory connectors and custom connectors run on the same infrastructure. See [directory vs custom](/docs/connectors/building/directory-vs-custom).
2222
23## Browsing the directory
23## Browse the directory
2424
2525Access the Connectors Directory through:
2626
2727* **[Customize > Connectors](https://claude.ai/customize/connectors)** in claude.ai
28* **[Organization settings > Connectors](https://claude.ai/admin-settings/connectors)** for Team/Enterprise admins
28* **[Organization settings > Connectors](https://claude.ai/admin-settings/connectors)** for Team and Enterprise Owners
2929
30## Requesting a connector on a Team plan
30On Team and Enterprise plans, an Owner adds a connector for the organization, and members then connect with their own account. On Enterprise plans, a member whose custom role includes managing the organization's libraries can add one too.
3131
32On Claude Team plans, members who do not have permission to enable connectors see a **Request** button on each directory connector instead of a connect action. Selecting **Request** sends the connector to your organization's admins for review. The button changes to **Requested** while the request is pending.
32## Request a connector on a Team plan
3333
34If you are a Team admin with permission to manage connectors, member requests appear in two places:
34On Claude Team plans, members who do not have permission to enable connectors see a **Request** button on each directory connector instead of a connect action. Selecting **Request** sends the request to your organization's Owners. The button changes to **Requested** while the request is pending.
3535
36* **[Organization settings > Connectors](https://claude.ai/admin-settings/connectors)** shows a **Requested by your team** section above the connector list.
37* **[Organization settings > Notifications](https://claude.ai/admin-settings/notifications)** lists each requested connector on the **Requests** tab, and the **Notifications** item in the admin sidebar shows a count badge while requests are pending.
36If you are an Owner on a Team plan, member requests appear in two places:
3837
38* **[Organization settings > Connectors](https://claude.ai/admin-settings/connectors)** shows a **Requested by your team** section above the connector list
39* **[Organization settings > Notifications](https://claude.ai/admin-settings/notifications)** lists each requested connector on the **Requests** tab, and the **Notifications** item in the admin sidebar shows a count badge while requests are pending
40
3941From either location you can enable the connector for your organization or dismiss the request. Claude shows the requesting member the outcome the next time they open the connectors directory.
4042
41## When a connector's endpoint changes
43## Recognize when a connector's endpoint changes
4244
4345Occasionally a provider updates the endpoint URL behind its directory listing, for example moving a server from `https://mcp.example.com/sse` to `https://mcp.example.com/mcp`. This is a routine change on the provider's side. Here is what you may notice in Claude:
4446
45* **Your existing connection keeps working.** Connectors you added before the change keep using the endpoint they were installed with, and your authentication is unaffected.
46* **It appears as a custom connector.** Because your connector no longer matches the updated directory listing, it shows under "Custom" in [Customize > Connectors](https://claude.ai/customize/connectors) instead of as a named directory connector.
47* **The directory listing shows as not installed.** Adding the connector from the directory again without removing the original gives you two connections: your original one and a new one on the updated endpoint.
47* **Your existing connection keeps working.** Connectors you added before the change keep using the endpoint they were installed with, and your authentication is unaffected
48* **It appears as a custom connector.** Because your connector no longer matches the updated directory listing, it shows under **Custom** in **[Customize > Connectors](https://claude.ai/customize/connectors)** instead of as a named directory connector
49* **The directory listing shows as not installed.** Adding the connector from the directory again without removing the original gives you two connections: your original one and a new one on the updated endpoint
4850
4951To move to the new endpoint, remove the connector and re-add it from the directory. Claude prompts you to authenticate with the service again.
5052
51## Submitting to the directory
53## Submit to the directory
5254
5355Organizations can submit their MCP servers for review and inclusion in the directory:
5456
551. Review the [submission guidelines](/docs/connectors/building/submission)
562. Ensure your server meets security and compatibility standards
573. Submit through the [submission portal](https://claude.ai/admin-settings/directory/submissions/new) in Claude.ai admin settings
57<Steps>
58 <Step title="Review the submission guidelines">
59 Review the [submission guidelines](/docs/connectors/building/submission).
60 </Step>
5861
59Submitting requires a Team or Enterprise organization and directory management access (organization Owners by default); see [Before you start](/docs/connectors/building/submission#before-you-start). After publication, the same dashboard shows your server's health and usage; see [Managing your listing](/docs/connectors/building/managing-your-listing).
62 <Step title="Meet the standards">
63 Ensure your server meets security and compatibility standards.
64 </Step>
6065
61## Related topics
66 <Step title="Submit in the developer portal">
67 Submit through the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage).
68 </Step>
69</Steps>
6270
63<Card title="Build a connector" icon="code" href="/docs/connectors/building/index">
64 Create your own MCP server.
65</Card>
71Anyone on a paid Claude plan can submit, and on Team and Enterprise an Owner submits; see [who can submit to the directory](/docs/directory/publish#confirm-you-can-submit-to-the-directory) for the role and organization requirements. After publication, the same dashboard shows your server's health and usage; see [Manage your directory listing](/docs/connectors/building/managing-your-listing).
72
73## Next steps
74
75* [Connector verification](/docs/connectors/verification): what the Verified and Community labels mean
76* [Get started with connectors](/docs/connectors/getting-started): set up a connector and use it in conversations
77* [Build an MCP server for Claude](/docs/connectors/building/index): create your own MCP server
6678
No line in this hunk matches that.