Answer Hub · Software & workflow

What is the RAZE MCP?

Reviewed by
Reviewed by RAZE
Last reviewed

Short answer

The RAZE MCP is the RAZE API offered as a Model Context Protocol server for MCP-compatible AI assistants and agents. Your team can order inspections and create projects, check status and history, pull reports, photos and questionnaire answers, and review capture metadata down to the data behind every photo.

What the RAZE MCP is.

The Model Context Protocol (MCP) is an open specification, published at modelcontextprotocol.io, for how an AI assistant connects to outside software through a defined set of tools. The RAZE MCP is RAZE's server on that protocol. It is the third way to order a RAZE draw inspection, beside the Ordering Engine and the RAZE API, and all three reach the same inspection workflow, the same report and the same record.

A person adds the RAZE MCP to an AI assistant, signs in with their own RAZE credentials and asks in plain language. From there a team can:

  • draft a project from an engagement letter and a schedule of values
  • order an inspection on the Marketplace or as a Direct Request
  • check status and history, or ask for a report on open work
  • pull the report, photos and questionnaire answers for a submitted inspection
  • review capture metadata: GPS location, date and time stamps, device type and ID, and the photo tags the app generates

What it is not.

The RAZE MCP does not approve draws or release funds. Your reviewer accepts or rejects each submitted inspection, unless your institution has turned on the auto-approve workflow setting, and the funding decision stays with the lender. The RAZE MCP does not change your LOS or core either. It reaches RAZE inspections only, and RAZE integrates with the Construction Loan Administration workflow you already run. The assistant also sees nothing more than the signed-in user can: if a user cannot see a project or order an inspection in RAZE, the assistant cannot do it for that user.

How RAZE handles it.

Your team connects with the RAZE credentials issued under your agreement. By default, the RAZE MCP shows a summary and waits for your confirmation before it creates or changes anything. A user can tell the assistant to skip that step, so set your team's rule: keep confirmation on. Actions taken through the RAZE MCP are logged in RAZE. The RAZE MCP works with the Stage sandbox, where orders reach no live inspector and nothing is billed, so a team can practice there first.

RAZE has tested the MCP with Claude, Claude Code, ChatGPT, Cursor and Microsoft Copilot (as of November 2026). Other MCP-compatible assistants and agents can connect. RAZE has not tested each one. Every way to order is included at no platform fee, the RAZE MCP among them, and your AI assistant subscription is separate.

The RAZE MCP FAQs answer the questions lenders ask next, and the setup page has the steps for each tested assistant. To begin, Get Started.

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.RAZE MCP FAQsRAZE
  3. 3.Set Up the RAZE MCPRAZE
  4. 4.Draw Inspection API & Developer PortalRAZE

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.

Get Started