Add a connector that isn't in the directory changedconnectors/custom/add-unlisted
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 20 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+101added
Lines−113removed
From line
6
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits4to this page, all time
The whole hunk
from line 6, old and new numbered
/
from line 6
66
77This page is for people adding a connector to their own Claude and for Team and Enterprise Owners adding one for their organization.
88
9<Note>
10 * If you want a service that's already in the directory, see the [Connectors Directory](/docs/connectors/directory) and connect it from there
11 * If you're building the server yourself, see [Build an MCP server for Claude](/docs/connectors/building/index)
12 * If your server runs inside your private network, see [MCP tunnels](/docs/connectors/mcp-tunnels/overview)
13</Note>
9> [!NOTE]
10>
11> * If you want a service that's already in the directory, see the [Connectors Directory](/docs/connectors/directory) and connect it from there
12> * If you're building the server yourself, see [Build an MCP server for Claude](/docs/connectors/building/index)
13> * If your server runs inside your private network, see [MCP tunnels](/docs/connectors/mcp-tunnels/overview)
1414
1515If you have a server URL, go to [Add a connector by URL](#add-a-connector-by-url). If you have a desktop extension, go to [Install a local connector in the desktop app](#install-a-local-connector-in-the-desktop-app).
1616
from line 27
2727
2828You can add any third-party connector as a custom connector as long as you have the URL of its remote MCP server. On Team and Enterprise plans, an Owner adds the connector for the organization, and members then connect with their own account.
2929
30<Warning>
31 Custom connectors allow connections to unverified services. Claude can access and perform actions within these services, so review [Security and privacy](#security-and-privacy) before you add one.
32</Warning>
30> [!WARNING]
31>
32> Custom connectors allow connections to unverified services. Claude can access and perform actions within these services, so review [Security and privacy](#security-and-privacy) before you add one.
3333
3434### On a Team or Enterprise plan
3535
from line 39
3939
4040Adding the connector in organization settings makes it appear under [**Customize > Connectors**](https://claude.ai/customize/connectors) for members, with the **Custom** label. To add it:
4141
42<Steps>
43 <Step title="Open organization connectors">
44 Go to [**Organization settings > Connectors**](https://claude.ai/admin-settings/connectors).
45 </Step>
42**1. Open organization connectors**
4643
47 <Step title="Add a custom connector">
48 Select **Add**, then **Custom**. If Claude asks for the connector type, choose **Web**.
49 </Step>
44Go to [**Organization settings > Connectors**](https://claude.ai/admin-settings/connectors).
5045
51 <Step title="Enter the server URL">
52 Enter the remote MCP server URL.
53 </Step>
46**2. Add a custom connector**
5447
55 <Step title="Enter OAuth credentials if needed">
56 Optionally, enter an OAuth client ID and secret. See [Choose authentication settings](#choose-authentication-settings).
57 </Step>
48Select **Add**, then **Custom**. If Claude asks for the connector type, choose **Web**.
5849
59 <Step title="Add the connector">
60 Click **Add**.
61 </Step>
62</Steps>
50**3. Enter the server URL**
6351
52Enter the remote MCP server URL.
53
54**4. Enter OAuth credentials if needed**
55
56Optionally, enter an OAuth client ID and secret. See [Choose authentication settings](#choose-authentication-settings).
57
58**5. Add the connector**
59
60Click **Add**.
61
6462#### Connect as a member
6563
6664Once an Owner has added the connector, each member connects to it with their own account:
6765
68<Steps>
69 <Step title="Open Customize > Connectors">
70 Go to **Customize > Connectors**.
71 </Step>
66**1. Open Customize > Connectors**
7267
73 <Step title="Find the custom connector">
74 Find the connector with the **Custom** label.
75 </Step>
68Go to **Customize > Connectors**.
7669
77 <Step title="Connect">
78 Click **Connect** to authenticate.
79 </Step>
80</Steps>
70**2. Find the custom connector**
8171
72Find the connector with the **Custom** label.
73
74**3. Connect**
75
76Click **Connect** to authenticate.
77
8278### On a Free, Pro, or Max plan
8379
8480You add custom connectors to your own account. On the Free plan, you can add one custom connector.
8581
86<Steps>
87 <Step title="Open Customize > Connectors">
88 Go to **Customize > Connectors**.
89 </Step>
82**1. Open Customize > Connectors**
9083
91 <Step title="Add a custom connector">
92 Click **Add custom connector**.
93 </Step>
84Go to **Customize > Connectors**.
9485
95 <Step title="Enter the server URL">
96 Enter the remote MCP server URL.
97 </Step>
86**2. Add a custom connector**
9887
99 <Step title="Enter OAuth credentials if needed">
100 Optionally, enter OAuth credentials. See [Choose authentication settings](#choose-authentication-settings).
101 </Step>
88Click **Add custom connector**.
10289
103 <Step title="Add the connector">
104 Click **Add**.
105 </Step>
106</Steps>
90**3. Enter the server URL**
10791
92Enter the remote MCP server URL.
93
94**4. Enter OAuth credentials if needed**
95
96Optionally, enter OAuth credentials. See [Choose authentication settings](#choose-authentication-settings).
97
98**5. Add the connector**
99
100Click **Add**.
101
108102### Choose authentication settings
109103
110104The layout of the **Add custom connector** dialog varies by organization. If yours shows a name, a URL, and **Advanced settings** on one screen, enter the OAuth client ID and secret under **Advanced settings**. If yours has two steps, it asks you to choose among the settings in this section.
from line 123
129123
130124### Authenticate with request headers
131125
132<Note>
133 Request header authentication is in beta and available to a limited set of organizations. If you don't see the **Request headers** section in the **Add custom connector** dialog, your organization doesn't have access yet.
134</Note>
126> [!NOTE]
127>
128> Request header authentication is in beta and available to a limited set of organizations. If you don't see the **Request headers** section in the **Add custom connector** dialog, your organization doesn't have access yet.
135129
136130If your MCP server authenticates with an API key, bearer token, or other fixed credential instead of OAuth, configure it in the **Request headers** section of the **Add custom connector** dialog. Claude stores each header value securely, doesn't show it again after you save, and sends it on every request to your server.
137131
from line 137
143137
144138A request header holds a fixed credential, such as an API key, that Claude stores and sends on every request to your server. To add one:
145139
146<Steps>
147 <Step title="Open Request headers">
148 In the **Add custom connector** dialog, open **Request headers**.
149 </Step>
140**1. Open Request headers**
150141
151 <Step title="Choose the header name">
152 Select a header name from the list, or choose **Custom header** to enter a different name. The list offers standard authentication and routing header names such as `authorization`, `x-api-key`, and `x-auth-token`, which every connector can use.
153 </Step>
142In the **Add custom connector** dialog, open **Request headers**.
154143
155 <Step title="Enter the value">
156 Enter the header value exactly as your server expects to receive it.
157 </Step>
144**2. Choose the header name**
158145
159 <Step title="Mark it required or optional">
160 Choose whether the header is **Required**. When a required header has no stored value at connection time, the connection fails. When an optional header has no value, Claude omits it from the request.
161 </Step>
146Select a header name from the list, or choose **Custom header** to enter a different name. The list offers standard authentication and routing header names such as `authorization`, `x-api-key`, and `x-auth-token`, which every connector can use.
162147
163 <Step title="Add more headers and save">
164 Repeat for any additional headers your server needs, then click **Add**. You can add up to four headers.
165 </Step>
166</Steps>
148**3. Enter the value**
167149
150Enter the header value exactly as your server expects to receive it.
151
152**4. Mark it required or optional**
153
154Choose whether the header is **Required**. When a required header has no stored value at connection time, the connection fails. When an optional header has no value, Claude omits it from the request.
155
156**5. Add more headers and save**
157
158Repeat for any additional headers your server needs, then click **Add**. You can add up to four headers.
159
168160Anthropic reviews and approves each custom header name before Claude sends it to a third-party server. This review prevents connector configuration from being used to send arbitrary header names. If you enter a header name that isn't approved, Claude rejects the save with an error. To request approval for a custom header name, contact [Claude support](https://support.claude.com/en/articles/9015913-how-to-get-support).
169161
170162#### Enter the full header value
from line 178
186178
187179You can edit a connector's name or URL, or remove the connector:
188180
189<Steps>
190 <Step title="Open your connectors">
191 Go to **Customize > Connectors**. If you're a Team or Enterprise Owner, go to **Organization settings > Connectors** instead.
192 </Step>
181**1. Open your connectors**
193182
194 <Step title="Remove or open the menu">
195 Click **Remove**, or select the three-dot menu.
196 </Step>
183Go to **Customize > Connectors**. If you're a Team or Enterprise Owner, go to **Organization settings > Connectors** instead.
197184
198 <Step title="Follow the prompts">
199 Follow the prompts.
200 </Step>
201</Steps>
185**2. Remove or open the menu**
202186
187Click **Remove**, or select the three-dot menu.
188
189**3. Follow the prompts**
190
191Follow the prompts.
192
203193You can't change authentication settings after you add a connector. That covers OAuth credentials and request headers. To change them, remove the connector and add it again with the new details. Members then need to reconnect.
204194
205195## Install a local connector in the desktop app
from line 200
210200
211201To install an extension you have as a `.mcpb` file:
212202
213<Steps>
214 <Step title="Open Settings > Extensions">
215 In the Claude desktop app, go to **Settings > Extensions**.
216 </Step>
203**1. Open Settings > Extensions**
217204
218 <Step title="Drag in the file">
219 Drag the `.mcpb` file onto the page. Claude opens a preview of the extension.
220 </Step>
205In the Claude desktop app, go to **Settings > Extensions**.
221206
222 <Step title="Install">
223 Select **Install**, then confirm.
224 </Step>
225</Steps>
207**2. Drag in the file**
208
209Drag the `.mcpb` file onto the page. Claude opens a preview of the extension.
210
211**3. Install**
212
213Select **Install**, then confirm.
226214
227215The extension then appears in the list on the **Extensions** page.
228216
No line in this hunk matches that.