Third party connectors with remote MCP changedconnectors/custom/remote-mcp
Nearest release: v2.1.251, published 7 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+36added
Lines−4removed
From line
35
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits5to this page, all time
## The Add custom connector dialog, field by field
The whole hunk
from line 35, old and new numbered
/
from line 35
35354. Optionally configure OAuth Client ID/Secret in Advanced settings
36365. Click "Add"
3737
38If your Add custom connector dialog has two steps, see [The Add custom connector dialog, field by field](#the-add-custom-connector-dialog-field-by-field).
39
3840**Members then:**
3941
40421. Go to **Customize > Connectors**
from line 51
49514. Optionally configure OAuth credentials
50525. Click "Add"
5153
54If your Add custom connector dialog has two steps, see [The Add custom connector dialog, field by field](#the-add-custom-connector-dialog-field-by-field).
55
5256### Enabling connectors in chat
5357
5458Use the "+" button in your chat interface to access "Connectors," where you can enable/disable connectors per conversation.
5559
60## The Add custom connector dialog, field by field
61
62<Note>
63 The two-step dialog described here is rolling out gradually. If your dialog shows a name, URL, and Advanced settings on one screen, your organization has the earlier version; the steps above still apply.
64</Note>
65
66**Name**: the display name shown in the connectors list.
67
68**Remote MCP server URL**: the HTTPS address where the server accepts MCP requests, for example `https://mcp.example.com/mcp`. After you continue, Claude checks the URL and pre-fills the authentication settings it detects, marked "Detected."
69
70**Authentication**: how people connect to the server.
71
72* **Always required**: each user signs in through the server's OAuth flow before using it.
73* **Required when the server asks**: Claude connects without credentials and prompts users to sign in when the server asks.
74* **None**: no sign-in. Anyone with access to the server URL can use the connector. If the server uses an API key, choose None and add the key under **Request headers**; Claude stores it as the connector's credential.
75
76**OAuth client** (shown unless you chose None): how Claude identifies itself to the server's authorization server.
77
78* **Use Anthropic's hosted client metadata** (recommended): the server reads Claude's client details from a URL Anthropic hosts (Client ID Metadata Document). Nothing to set up; the server must support it.
79* **No client ID — register one automatically**: Claude registers OAuth clients with the server as users connect (Dynamic Client Registration). Works with most servers, but adds client registrations over time.
80* **Use your own OAuth client**: enter a client ID you registered with the server. Leave the secret blank unless your authorization server requires one. See [Authentication for connectors](/docs/connectors/building/authentication).
81
82**Request headers**: fixed credentials such as API keys, sent on every request. See [Authenticating with request headers](#authenticating-with-request-headers).
83
84**Advanced > Transport**: set from the URL automatically; a URL ending in `/sse` selects the older SSE transport. Change it only if the server's documentation says to.
85
5686## Authenticating with request headers
5787
5888<Note>
59 Request header authentication is in beta. This feature is being slowly rolled out to customers; contact Anthropic for early access.
89 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.
6090</Note>
6191
6292If your MCP server authenticates with an API key, bearer token, or other fixed credential instead of OAuth, you can configure it in the **Request headers** section of the Add custom connector dialog. Claude stores each header value securely, does not show it again after you save, and sends it on every request to your server.
from line 118
88118
89119## Managing connectors
90120
91To remove or edit connectors:
121To edit a connector's name or URL, or to remove a connector:
92122
931. Go to **Customize > Connectors**
1231. Go to **Customize > Connectors** (Team and Enterprise owners: **Admin settings > Connectors**)
941242. Click "Remove" or select the three-dot menu
953. Follow prompts to edit or remove
1253. Follow the prompts
126
127Authentication settings (OAuth credentials and request headers) can't be changed after a connector is added. To change them, remove the connector and add it again with the new details. Members will need to reconnect.
96128
97129## Security and privacy
98130
No line in this hunk matches that.