Source: https://qbash.com/docs/clients/claude # How to add a custom connector to Claude To add a custom connector to Claude, go to **Customize**, then **Connectors**, choose **+ Add**, then **Add custom connector**, and paste the remote MCP server's URL. On Team and Enterprise, an Owner adds it for the organization first. A connector added on claude.ai also appears in the Claude desktop app and the mobile apps, and in Claude Code when you sign in to it with the same Claude account. Add it on the web or the desktop app, then use it anywhere. ## Who can add a custom connector | Plan | Add a custom connector | Use one an Owner added | |---|---|---| | Free | Yes, one custom connector | Not applicable | | Pro, Max and Ultra | Yes | Not applicable | | Team | Owners and Primary Owners only | Yes. Each member connects it and signs in | | Enterprise | Owners, Primary Owners, and custom roles with Libraries set to **Manage** | Yes, if the member's role includes the connector | On Team and Enterprise, no organization setting lets every member add their own custom connectors. Members can ask for one when **Let members request connectors** is on. It is on by default for Team and off for Enterprise. Sources: Anthropic's [custom connectors guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp), [connectors help](https://support.claude.com/en/articles/11176164), [Enterprise custom roles](https://support.claude.com/en/articles/13930452) and [remote MCP connector docs](https://claude.com/docs/connectors/custom/remote-mcp), checked 2026-11-04. :::note[Here from Google? Hi, we make the server in the screenshots] - qbash runs Tasks, which are Python programs with AI steps, alongside your connected accounts and shared memory folders. Claude can call all of it as tools. - You don't need qbash to follow this guide. Any remote MCP server goes in the same dialog. [What the qbash server does](https://qbash.com/docs-markdown/mcp-servers/official-mcp-server.md) ::: ## Free, Pro, Max and Ultra 1. Go to **Customize**, then **Connectors**, choose **+ Add** and then **Add custom connector**. 2. Enter a name such as "qbash", paste `https://mcp.qbash.com/mcp` as the URL and choose **Continue**. 3. Claude shows the authentication settings it found on the server. Choose **Continue**. 4. Under **Authentication**, choose **Sign in now**. Under **OAuth client**, choose **Register automatically**, then choose **Add**. 5. Sign in to qbash in the window that opens, pick the qbash organization Claude should use and choose **Allow**. Some accounts show the name, URL and **Advanced settings** on one screen instead. Enter the name and URL there and choose **Add**. If the dialog has a **Request headers** section, leave it empty. qbash signs each person in through OAuth. ## Team and Enterprise An Owner can add a connector under **Customize**, then **Connectors**, the same way as on a personal plan, but that connector is only for the Owner. To add it for the whole organization: 1. Open **Organization settings**, then **Connectors**, and choose **Add**. 2. Choose **Custom**, then **Web**. 3. Enter the name and URL and finish the same screens as above. Members then go to **Customize**, then **Connectors**, find qbash (usually labelled **Custom**) and choose **Connect**. Each member signs in to qbash with their own account. On Team, only Owners and Primary Owners can add connectors. On Enterprise, a custom role that includes **Manage access to Libraries** can as well. Don't add a token under **Request headers** for an organization connector. Every member would then use that one qbash account. ## Use it in a chat Choose the **+** button at the bottom of the message box, then **Connectors**, and turn qbash on for that conversation. Anthropic's [custom connectors guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) has the full details.