One read of Claude Documentationclaude-docs-20260828T073717Z
3 pages moved out of 216 read.
Pages moved
3
significant first
Pages read
216
in this capture
Captured
07:37 UTC
Corpus hash
87285e4f0124
corpus-hash
What this read moved
1-3 of 3claude-tag/admins/restrict-access Changed · +10 / -1 lines
from line 80
8080
8181To keep Claude out of channels by name ahead of time, add a [blocked channel pattern](#block-or-auto-join-channels-by-name) instead.
8282
83Steps 1–3 do not delete any data. Step 4 (removing the scope) deletes the channel's data. Step 5 (deleting a bundle) removes the credentials in that bundle; memory, routines, and session transcripts are unaffected. Removing Claude from a channel stops it responding there; the channel's memory and routines remain on record, and re-adding it restores them. To delete data without uninstalling, use the dedicated controls at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag).
83Steps 1–3 do not delete any data. Removing Claude from a channel stops it responding there; the channel's memory and routines stay on record, and re-adding Claude restores them.
84
85Steps 4 through 6, and disconnecting the workspace, each delete something different:
86
87* **Remove the channel's scope (step 4):** deletes the channel's sessions, memory, routines, and published artifacts. Claude keeps answering in the channel with the access it inherits from its workspace; see [what each action deletes](/docs/claude-tag/concepts/data-lifecycle#actions-in-claude).
88* **Delete the bundle (step 5):** removes the credentials in that bundle. Memory, routines, and session transcripts stay.
89* **Uninstall the app (step 6):** Anthropic deletes the workspace's Claude data, the same set as disconnecting the workspace, plus the app's installation credential; see [what each action deletes](/docs/claude-tag/concepts/data-lifecycle#actions-in-slack).
90* **[Disconnect the workspace](/docs/claude-tag/admins/workspaces#revoke-a-pairing)** at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag): Anthropic deletes the workspace's sessions and transcripts, memory, routines and artifacts, scopes, and members' account links, and the app stays installed so a workspace admin can pair again; see [what each action deletes](/docs/claude-tag/concepts/data-lifecycle#actions-in-claude).
91
92Access bundles belong to your organization, not to a workspace, so uninstalling or disconnecting keeps them; only their bindings to that workspace's scopes go. To delete one channel's data while Claude stays in the workspace, remove that channel's scope (step 4) rather than uninstalling.
8493
8594### Limit Claude Tag to specific channels
8695
connectors/custom/remote-mcp Changed · +36 / -4 lines
## The Add custom connector dialog, field by field
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
claude-tag/admins/connections/custom Changed · +2 / -0 lines
from line 90
9090
9191## Add a custom MCP server
9292
93The server must be a remote endpoint that Claude can reach at a URL over the internet. An MCP server that runs on a person's machine over stdio, including one packaged as a [desktop extension](/docs/connectors/custom/desktop-extensions), can't be connected, because [sessions](/docs/claude-tag/concepts/glossary#session) run in a cloud sandbox that Anthropic hosts, not on anyone's machine. Host the server as a remote endpoint first, then follow the steps below.
94
9395To give Claude an MCP server (one you run, or a vendor's hosted MCP endpoint), the pattern is a plugin plus a credential:
9496
9597<Steps>