Custom connectors changedclaude-science/custom-connectors
Nearest release: v2.1.275, published 5 hours 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 17 Sep 2026 15:04 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+3added
Lines−3removed
From line
10
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 10, old and new numbered
/
from line 10
1010
1111Every tool from a custom connector starts as **Not set**, and Claude asks before using it. On the connector's page, set individual tools to **Always allow**, **Ask each time**, or **Block** under **Tools**, or turn on Skip approvals for the whole connector.
1212
13<Warning>
14 Skip approvals disables the per-call card for every tool on that connector. Only use connectors from developers you trust.
15</Warning>
13> [!WARNING]
14>
15> Skip approvals disables the per-call card for every tool on that connector. Only use connectors from developers you trust.
1616
1717Local-command connectors run inside the sandbox with the same network limits as Claude's code and a per-connector writable directory. Environment variables for local connectors are saved unencrypted in a configuration file readable by your account only; don't put high-value secrets there. On Windows, a local-command connector starts with `npx`, `node`, `python`, or the full path of a program. Connectors launched through `npm` or a `.cmd`, `.bat`, or `.ps1` file aren't supported there.
1818
No line in this hunk matches that.