FAQ

RAZE MCP FAQs

The RAZE MCP is the third way to order a RAZE draw inspection, beside the Ordering Engine and the RAZE API.

Reviewed by RAZE ·

What is the RAZE MCP?

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.

Set up the RAZE MCP

What is the Model Context Protocol (MCP)?

The Model Context Protocol is an open specification for how an AI assistant connects to outside software through a defined set of tools. It is published at modelcontextprotocol.io. RAZE uses it so the assistant your team already works in can reach RAZE inspections with each user's own RAZE permissions.

Read how ordering through the MCP works

Which AI assistants work with the RAZE MCP?

The RAZE MCP works with MCP-compatible AI assistants and agents. RAZE has tested it with Claude, Claude Code, ChatGPT, Cursor and Microsoft Copilot (as of November 2026). Other MCP-compatible assistants can connect, though RAZE has not tested each one. Some business plans need an administrator to allow custom connectors first.

Set up the RAZE MCP

How is the RAZE MCP different from the RAZE API?

The RAZE API is for developers who connect a loan system to RAZE. The RAZE MCP offers the same API to an AI assistant, so a person can ask in plain language. Both reach the same RAZE data with the user's own permissions, and both work beside your LOS and core.

See the Developer Portal

Does the RAZE MCP replace the Ordering Engine?

No. There are three ways to order a RAZE draw inspection: the Ordering Engine, the RAZE API and the RAZE MCP. All three reach the same inspection workflow, the same report and the same record. A team can order in the Ordering Engine and review from an assistant, or the reverse.

See the Ordering Engine

Does the RAZE MCP approve draws?

No. The RAZE MCP lets an assistant order inspections and retrieve inspection data. It 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.

See how RAZE uses AI in draw inspections

What can my team do through the RAZE MCP?

Your 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, ask for a report on open work, check status and history, and pull the report, photos and questionnaire answers for a submitted inspection.

Read the Bring Your Own AI post

Can an assistant create a project or order an inspection without asking me?

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. Most lenders will want a simple team rule: keep confirmation on for anything that creates or changes a record.

Read how ordering through the MCP works

Can the assistant see more than I can in RAZE?

No. The assistant works through the same RAZE API as the Ordering Engine, inside the signed-in user's own RAZE permissions. If a user cannot see a project or order an inspection in RAZE, the assistant cannot do it for that user. Access is managed in RAZE the way it is today.

Set up the RAZE MCP

Are actions taken through the RAZE MCP logged?

Yes. Actions taken through the RAZE MCP are logged in RAZE. An order placed from an assistant creates the same inspection record as an order placed in the Ordering Engine or by API, with the same history of status changes and who made them.

See how RAZE supports audit and exam review

How does my team get access to the RAZE MCP?

Your team connects with the RAZE credentials issued under your agreement. Each person adds the RAZE MCP to an AI assistant and signs in with their own RAZE credentials. The assistant can then do only what that user's RAZE permissions allow.

Set up the RAZE MCP

Can we practice before placing a live order?

Yes. The RAZE MCP works with the Stage sandbox. Orders placed on Stage reach no live inspector and nothing is billed, so a team can practice creating projects and ordering inspections from an assistant before it works on live loans.

See the Developer Portal

Does the RAZE MCP cost extra?

No. Every way to order a RAZE draw inspection is included with no platform fee, the RAZE MCP among them. An inspection ordered from an assistant is priced on the same published Rate Card. Your AI assistant subscription is separate and set by its provider.

See the Rate Card

Where does our data go when we use an AI assistant?

Data your team requests through the RAZE MCP moves from RAZE to the AI assistant your institution connected. How that assistant stores or uses the data is governed by your agreement with its provider and your plan's administrator settings. Include those terms in your vendor review. The inspection record stays in RAZE.

See how RAZE supports audit and exam review

What controls should a lender set before connecting an AI assistant?

Common controls are simple. Decide which assistants your team may connect. Give each user the RAZE role the job needs and no more. Keep confirmation on for anything that creates or changes a record. Limit who can add connectors. Have a reviewer check summaries against the report.

Read how ordering through the MCP works

Does the RAZE MCP change our LOS or core?

No. RAZE works beside the systems you already run and integrates with your existing Construction Loan Administration workflow. The RAZE MCP reaches RAZE inspections only. Your loan records stay exactly where they are, and the inspection record stays in RAZE.

See where RAZE sits in the lending stack

Can an assistant's summary replace reading the inspection report?

No. A summary is a starting point for review. The reviewer reads the report, the photos and the draw sheet before deciding what to fund. RAZE documents the inspection, the assistant helps find and organize it, and the lender's reviewer makes the decision.

See what is in a draw inspection report

We are a software platform. Should we build on the RAZE API or the RAZE MCP?

Build product integrations on the RAZE API, with the OpenAPI reference and the Stage sandbox in the Developer Portal. Use the RAZE MCP to try a workflow in plain language before code is written, and to support users who work in an AI assistant. Both reach the same RAZE data.

See the Developer Portal

Answer Hub

Short answers on this topic

Browse every answer →