--- title: "Setting Up Built Partner MCP in Claude & ChatGPT" slug: "setting-up-built-partner-mcp-in-claude-chatgpt" updated: 2026-11-18T22:26:24Z published: 2026-11-18T22:26:24Z canonical: "help.getbuilt.com/setting-up-built-partner-mcp-in-claude-chatgpt" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.getbuilt.com/llms.txt > Use this file to discover all available pages before exploring further. # Setting Up Built Partner MCP in Claude & ChatGPT ### **Purpose** Built Partner MCP is a remote MCP (Model Context Protocol) server that lets an AI assistant read and act on your organization's Built data directly in a chat, limited to each user's own Built permissions. You connect to it with **one URL**. There's no software to install, no API key to paste, and no client ID or secret to manage. Each user signs in through their browser with their own Built login, and Claude or ChatGPT can then see only the data that user is allowed to see. For an introduction to Partner MCP, see [Built Partner MCP Overview](/lending/docs/built-partner-mcp-api-overview). | Setting | Value | | --- | --- | | **Connector / server URL** | Provided by Built | | **Authentication** | OAuth (browser sign-in). No API key, client ID, or secret to enter. | | **Identity** | Each user signs in with their own Built account. All data access is limited to that user. | | **Who sets it up** | Claude: an organization **Owner**. ChatGPT: a workspace **Admin/Owner**. | | **Who signs in** | Every user connects and signs in individually after the connector is added. | --- ### **Target Users** Claude organization Owners and ChatGPT workspace Admins/Owners who add the Built connector for their organization, and the users who then connect to it. --- ### **How It Works** #### Before You Begin: Coordinate with Built Two things must be in place on Built's side **before** anyone in your organization can sign in. Confirm both with your Built representative: 1. **Your Built tenant is enabled for Partner MCP.** Contact your Built representative to get access. 2. **Single sign-on, if your users use it.** If your Built users sign in through your own identity provider (such as Okta or Entra ID) instead of a Built password, Built must set up that provider for MCP sign-in first. Give your Built contact the identity provider name they ask for. If your users sign in to Built with a Built username and password, no SSO setup is needed. > [!NOTE] > Note: > > - Built doesn't need to allowlist your Claude or ChatGPT organization. #### Plan and Role Requirements | Platform | Plan needed to add an organization connector | Who can add it | | --- | --- | --- | | **Claude** (desktop, web, and Cowork) | Team or Enterprise (custom connectors also work on Free, Pro, and Max per user) | An **Owner** (Team). On Enterprise, an Owner or a custom role with **Manage access to Libraries** | | **ChatGPT** | Business or Enterprise/Edu | A workspace **Admin/Owner**. On Enterprise, developer access can be delegated through RBAC | #### Claude: Add the Connector for Your Organization (Owner) Claude's organization connectors apply across every Claude surface your users use: the Claude desktop app, Claude in the browser, and Cowork. You set up the connector **once** at the organization level, and each user then connects it to their own account. 1. Go to **Organization settings** > **Connectors**. 2. Click **Add**. 3. Hover over **Custom**, then select **Web**. 4. Enter a **Name** your users will recognize, such as **Built Partner Connector**. 5. Enter the remote MCP server URL provided by Built, then click **Continue**. 6. Claude detects the connector's authentication settings. Review them and click **Continue**. 7. Set the options as follows: - **Authentication**: Choose **Sign in when needed**. Each user signs in with their own Built login the first time they use the connector. - **OAuth client**: Choose **Use Claude's published identity (Recommended)**. Don't choose **Register automatically**, because Built doesn't support it and setup will fail. Don't choose **Use your own OAuth client**, because no client ID or secret is needed. - **Request headers**: Leave empty. The Built connector uses OAuth, not an API key. 8. Click **Add** to finish. The connector now appears in your users' connector lists with a **Custom** label. > [!NOTE] > Note: > > - Use the **Connectors** feature, not a config file. Claude Desktop also supports local MCP servers through a `claude_desktop_config.json` file, but that's a different setup. Built Partner MCP is a remote connector added through settings, so it works the same in the desktop app, the browser, and Cowork, and it's managed centrally. > - Claude connectors can't be edited. If the URL or a setting changes, remove the connector and add it again with the new details. #### Claude: Connect and Sign In (Each User) 1. Go to **Settings** > **Connectors**. 2. Find **Built Partner Connector** (it has a **Custom** label) and click **Connect**. 3. A browser tab opens on Built's **Connect your MCP client to Built** page. Enter your work email. Built routes you based on how your organization signs in: either **Continue with SSO** to your identity provider, or a Built password form with your email filled in. 4. When sign-in is complete, the tab returns to Claude and the connector shows as connected. #### ChatGPT: Turn On Developer Mode and Add the Connector (Admin) ChatGPT offers custom MCP connectors through **developer mode**, available on Business and Enterprise/Edu workspaces on the web. A workspace admin turns on the capability and publishes the connector. Users then turn it on and sign in individually. > [!NOTE] > Note: > > - OpenAI's custom connector experience is in beta, and its labels and menu paths change. If a label differs from these steps, follow OpenAI's help article [Developer mode and MCP connectors in ChatGPT](https://help.openai.com/en/articles/12584461) and keep the values from this article. 1. In **Workspace Settings** > **Permissions & Roles** > **Connected Data**, turn on **Developer mode / Create custom MCP connectors**. - On **Business**, each admin or owner turns this on for themselves. It doesn't carry over to other admins automatically. - On **Enterprise/Edu**, you can give developer access to selected roles through RBAC and control who can use each published connector. 2. Create the custom MCP connector and enter: - **Name**: For example, **Built Partner MCP**. - **Server URL / MCP server URL**: The URL provided by Built. - **Authentication**: **OAuth**. ChatGPT finds Built's OAuth settings automatically, so there's nothing to type. - Leave any client ID, secret, or API key fields empty. 3. Acknowledge the risk notice and create the connector. 4. **Publish it to the workspace** (through the workspace **Apps** / **Drafts** area) so users see it in their approved connectors list. Published connectors show a **custom** label. #### ChatGPT: Turn On and Sign In (Each User) 1. In ChatGPT, go to **Settings** > **Plugins** > **Browse Plugins** > **[Your Org]** > **Built Partner MCP** > **Install Plugin**. 2. ChatGPT opens Built's sign-in page in a browser tab. Enter your work email and complete sign-in the same way as for Claude: SSO or Built password. 3. When sign-in is complete, the tab returns to ChatGPT. --- ### **Best Practices** - Confirm with your Built representative that your tenant is enabled, and that SSO is set up if your users need it, before anyone tries to sign in. - In Claude, choose **Use Claude's published identity (Recommended)**. Don't choose **Register automatically** or **Use your own OAuth client**. - In ChatGPT, leave client ID, secret, and API key fields empty.