New: AI-assisted search! Ask questions and follow-ups in full sentences for smarter, faster help. Try asking things like: “How do I change a builder's or borrower's email address?”

Built Partner MCP Overview

Prev Next

Purpose

The Built Partner MCP lets your team use an AI assistant, such as Claude, ChatGPT, Microsoft Copilot, or Snowflake Cowork, to work with Built on their behalf: look up a loan, check a draw's status, or update a record. Your organization can connect its own AI assistants to Built data and workflows without custom integration work.

Partner MCP is available for Construction Loan Administration+ (CLA+), Construction Financials, and Deal Management.

Partner MCP access includes Built's Partner API, so your developers can also build direct integrations with your Built data. Contact your Built representative to learn more.


Key Features

  1. Supported AI assistants: Connect Built to Claude, ChatGPT, Microsoft 365 Copilot (through an agent built in Microsoft Copilot Studio), or Snowflake Cowork. Built accepts connections only from approved AI assistants.

  2. Sign in with your Built account: Each user connects with their own Built account, including through your organization's single sign-on (SSO) where it's configured. The AI assistant never sees the user's password.

  3. Your Built permissions apply: A connected assistant can see and do exactly what the signed-in user can see and do in Built: no more, no less. It can't reach anything the user couldn't already open themselves.

  4. Control what the assistant can do: Your organization can set a limit for everyone:

    • Not restricted: Assistants can do anything the user can.

    • No deletes: Assistants can read, create, and update.

    • Read only: Assistants can look up data, not change it.

  5. Skills: Pre-built instructions help your assistant handle common Built workflows, such as reviewing a draw, summarizing a loan, or checking budget status.


Target Users

Built users who want to work with Built through an AI assistant, and the IT or AI administrators who set up the connection for their organization.


How It Works

Getting Started

  1. Contact your Built representative to add Partner MCP to your contract.

  2. Built turns on Partner MCP for your organization. Users who will connect an AI assistant need MCP access in their Built permissions.

  3. Your administrator receives the connection details from Built and sets up your AI assistant. See the setup article for your AI assistant under Support & Resources.

  4. Each user connects to Built from the AI assistant and signs in with their own Built account.

Note:

  • If your organization signs in to Built with SSO, Built completes a one-time setup step before your users can connect. Your Built representative will confirm timing.

Signing In

  1. The first time a user connects their AI assistant, Built's sign-in page opens in their browser.

  2. The user enters their work email. Built routes them to the sign-in method your organization uses, including your SSO provider where one is configured.

Note:

  • Connections last up to one day from sign-in. After that, users sign in again to reconnect.

What Isn't Available Today

The following actions aren't available through Partner MCP:

  • Paying out funds

  • Creating users

  • Changing user permissions

  • Configuring draw and deal workflows

Sharing Feedback and Reporting Issues

  • Feedback: Users can submit feedback to Built directly from their conversation with the AI assistant.

  • Issues: If something isn't working, download your conversation and send it to Built Support with a description of the problem.


Benefits

  • Work with Built from the AI assistant your team already uses.

  • Connect AI assistants to Built data and workflows without custom integration work.

  • Keep Built's existing user identity, permissions, and access controls in place for every user.


Best Practices

  • Consider starting read-only, then expanding what the assistant can do as your team gets comfortable.

  • Before full rollout, test with at least two users who have different Built permissions to confirm each user sees only what they should.

  • Never set up the connection with a shared Built account or an administrator's credentials. Each user signs in as themselves.

  • Review your AI provider's enterprise terms and admin controls, the same way you would for any tool that handles customer information.


Support & Resources


FAQ

Can the assistant approve a draw?

Only if the signed-in user could approve it in Built. This also applies to pay applications and change orders. The approval is recorded as that user's, the same as in Built. If users shouldn't act on approvals through an assistant, they can connect read-only, or your organization can set a read-only limit for everyone.

Can an assistant run on its own, without a person?

No. Every connection starts with a person completing an interactive sign-in. Partner MCP can't give an assistant standing, unattended access.

Where does our data go when the assistant reads it?

To the AI assistant the user connected, and from there to that assistant's provider. What happens to the data next, such as retention and model training, is governed by your organization's agreement with that AI provider. Built doesn't use your data to train AI models.

Does Built store our data or credentials in the connection?

No. Partner MCP passes requests between the AI assistant and Built and doesn't store customer records or access credentials. Your data stays in Built under the same controls that apply today.

Why do I need to sign in again?

Connections last up to one day from sign-in, even if you're using them the whole time. Sign in again to reconnect.

Can we use an AI assistant that isn't listed?

Built accepts connections only from approved AI assistants. Other tools may need additional setup. Contact your Built representative to ask about a tool that isn't listed.

Footer Example