Transaction, contract and mortgage MCPs

By the Goliath research team · Checked November 12, 2026

A transaction MCP connects Claude or ChatGPT to e-signature, transaction checklists, title work and mortgage paperwork. DocuSign and Rechat have official servers, and dotloop, title and mortgage tools have community ones.

What a transaction MCP lets the AI do

Track status. "Which contracts are still waiting on a signature?"
Chase signers. Send a reminder to whoever's turn it is.
Read documents. Pull the numbers out of a Loan Estimate or a purchase agreement.
Prepare, sometimes send. Some servers create and send an agreement from a template.

New to MCPs? The real estate MCP guide explains how the connection works.

DocuSign (official)

DocuSign's MCP server became generally available on September 30, 2026. Through it, the AI creates, sends and tracks agreements.

Rechat (official, for agents)

Rechat's official MCP covers contacts, marketing and deals for agents and brokerages. Broader access to its AI connection is by waitlist.

dotloop and SkySlope

We found no official MCP server from dotloop or SkySlope as of November 11, 2026.

Title and mortgage (community)

Mortgage documents. A community server turns Loan Estimate and Closing Disclosure PDFs into data for comparing loan offers.
Title work. A community server handles title and closing tasks such as OFAC screening and mortgage release searches.
Mortgage math. The open-source agentic-ops real estate server adds mortgage and investment calculations to property search.

None come from a lender or title company, so check their output against the real documents.

What the AI can do, and what a person still does

Tool	The AI can	A person still
DocuSign	Create, send and track agreements	Approves what's sent; signs
Rechat	Work with deals and contacts	Runs the transaction
dotloop (community, Zapier)	Read loops; Zapier actions	Gets API approval; sends
Mortgage, title (community)	Read documents, run checks	Verifies against the originals
Goliath	Find templates, check who signed, remind signers, track the deal	Prepares and sends each new contract in the app

Where Goliath fits

Goliath has built-in contracts for investors sending purchase agreements to sellers. Through its MCP, the AI sees templates and contracts, checks who has signed and sends reminders.

The AI can't send a new contract. Prompts that work today:

"Which of my contracts are still waiting on the seller?"
"Remind everyone whose turn it is to sign on the Oak Street contract."
"Show me the contracts on this deal."
"What contract templates do we have, and which ones are ready to send?"
"Create a deal for 123 Oak Street and add a task to send the purchase agreement tomorrow."

Things to check before you connect

Know who sends. If a server can send agreements on its own, turn that off unless you want it.
Watch the template, not only the AI. Most errors come from a wrong template or missing field, not the AI's wording.
Signer identity. Good systems verify signers with a code or an email link.
This isn't legal advice. Contract rules vary by state.

Questions

Can the AI sign for me? No, signing stays with the person signing.

Is there a free option? DocuSign's demo endpoint is free for testing, and community title and mortgage servers are free code. Sending real agreements needs a paid plan.

Can one AI connection handle the deal and the contract? Yes, if they live in one system, as they do in Goliath.

See every server we know of in the directory, or what separate tools cost on the cost page.