Answer Hub · Software & workflow

How can a lender order draw inspections with an MCP server?

Reviewed by
Reviewed by RAZE
Last reviewed

Short answer

A lender connects an MCP-compatible AI assistant or agent to the RAZE MCP server, each person signing in with their own RAZE account. The team names the project and address in plain language, the assistant collects the order details and shows a summary, and a person confirms before the order is placed on the Marketplace or as a Direct Request.

How an order moves through the MCP.

The Model Context Protocol (MCP) is an open specification, published at modelcontextprotocol.io, for how an AI application talks to a server that offers tools, so an assistant can act on a system it was not built into. The RAZE MCP server is RAZE's side of that connection; what it is and everything it exposes are on the platform page and the Developer Portal page. This page covers ordering only.

  1. Connect. In the Developer Portal, follow the setup for the RAZE MCP server for your assistant. Each person signs in with their own RAZE account, so there is no token to copy, and the assistant can only do what that account's RAZE permissions allow. Stage is a sandbox where orders never reach a live inspector and nothing is billed, so a team can practice there first.
  2. Ask. Name the project and the property address in plain language. If the project is new to RAZE, ask the assistant to create it first.
  3. Choose. The assistant collects the order details: Marketplace, where RAZE sends a background-checked inspector, or Direct Request, where you name your own staff inspector or vendor. It can find nearby inspectors if you ask.
  4. Confirm. The assistant shows a summary of the order. Nothing is placed until a person says yes; every write in RAZE waits for that confirmation and is logged to the user who gave it.
  5. Follow. The assistant can report the inspection's status and history and, once the report is submitted, pull the report, photos and questionnaire answers, along with the capture metadata behind each photo: GPS location, date and time stamps, device type and ID, and the photo tags the app generates.

Why it matters for lenders.

Ordering through an assistant lets a team work from the tools it already uses without opening another system. An order placed through the MCP creates the same record as an order placed in the Ordering Engine or by API: the same inspector workflow and the same report. When an auditor or examiner later reads the file, they read the same inspection record, whichever way it was ordered, and the log shows which user confirmed it. Any tool that can connect to a custom MCP server qualifies; the Bring Your Own AI post shows worked prompts.

How RAZE handles it.

The RAZE MCP server works inside MCP-compatible AI assistants and agents and gives them the same operations as the RAZE API: create projects, order inspections on the Marketplace or as a Direct Request, check status and history, and pull reports, photos, questionnaire answers and capture metadata. The assistant drafts the order; a person confirms it.The lender's reviewer accepts or rejects each submitted inspection, unless the institution has turned on auto-approve, a workflow setting rather than an AI decision, and funding stays the lender's decision. Orders placed through the MCP carry the same per-inspection rates as any other order; see pricing. To get started, Request a Demo.

Sources

Primary sources only. Where a figure appears on this page, it comes from one of these.

  1. 1.Model Context Protocol specification (revision 2026-07-28)Model Context Protocol · modelcontextprotocol.io
  2. 2.Draw Inspection Software for Construction LendersRAZE
  3. 3.Draw Inspection API & Developer PortalRAZE
  4. 4.RAZE Can Do That: Bring Your Own AI to Draw InspectionsRAZE

See the workflow behind the answer.

RAZE standardizes how draw inspections are ordered, dispatched, captured and delivered, inside the loan administration workflow a lender already runs.

Request a Demo