The whole hunk
from line 2, old and new numbered
/
lines
from line 2
22
33> Add any Model Context Protocol (MCP) server as a Remote (HTTPS web server) or Local command (program on your computer).
44
5In **Settings > Connectors** > **Add connector**, choose Remote or Local command and enter a **Name** (lowercase letters, digits, hyphens). For Remote, enter the server URL; Advanced settings covers transport (**SSE** or **Streamable HTTP**), OAuth client settings, and the **Headers helper command**. For Local command, enter the command; Advanced settings covers arguments and environment variables. **Browse Connectors Directory** opens the public directory.
5In **Settings > Connectors** > **Add connector**, choose **Remote** or **Local command** and enter a **Name** (lowercase letters, digits, hyphens). For **Remote**, enter the server URL; **Advanced settings** covers transport (**SSE** or **Streamable HTTP**), OAuth client settings, and the **Headers helper command**. For **Local command**, enter the command; **Advanced settings** covers arguments and environment variables. **Browse Connectors Directory** opens the public directory.
66
77Remote servers that need login take you through the provider's sign-in page.
8
9On Team and Enterprise plans, you can add and use custom connectors only if your organization allows them. When it doesn't, the **Remote** and **Local command** options under **Add connector** are grayed with a note that custom connectors are disabled by your admin. Custom connectors you added earlier stay listed and grayed, Claude can't use them, and they work again if your organization turns custom connectors back on. See [Custom connectors](/docs/claude-science/admin-controls#custom-connectors) in the admin controls.
810
911Every tool from a custom connector starts at **Ask each time**. On the connector's page, set individual tools to **Always allow** or **Block** under **Tools**, or turn on Skip approvals for the whole connector.
1012