Third party connectors with remote MCP changedconnectors/custom/remote-mcp
Nearest release: v2.1.268, published under an hour 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+7added
Lines−7removed
From line
65
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits5to this page, all time
The whole hunk
from line 65, old and new numbered
/
from line 65
6565
6666**Name**: the display name shown in the connectors list.
6767
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."
68**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."
6969
7070**Authentication**: how people connect to the server.
7171
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.
72* **Sign in now**: each user signs in through the server's OAuth flow before using it.
73* **Sign in when needed**: Claude connects without credentials and prompts users to sign in when the server asks.
74* **No sign-in**: anyone with access to the server URL can use the connector. If the server uses an API key, choose **No sign-in** and add the key under **Request headers**; Claude stores it as the connector's credential.
7575
76**OAuth client** (shown unless you chose None): how Claude identifies itself to the server's authorization server.
76**OAuth client** (shown unless you chose **No sign-in**): how Claude identifies itself to the server's authorization server.
7777
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.
78* **Use Claude's published identity** (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* **Register automatically**: Claude registers OAuth clients with the server as users connect (Dynamic Client Registration). Works with most servers, but adds client registrations over time.
8080* **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).
8181
8282**Request headers**: fixed credentials such as API keys, sent on every request. See [Authenticating with request headers](#authenticating-with-request-headers).
No line in this hunk matches that.