MCP, in operator language
MCP for CRE: connect Claude to the systems your firm already runs
Generic MCP explainers tell you what the standard is. This one answers the question a CRE team actually has: what changes about the work once Claude can read the deal folder, the property exports, and the email thread where the deal is really being negotiated.
By Zed Truong, Co-founder, Pacific Software VenturesPublished · Updated
Short answer
MCP (Model Context Protocol) is the open standard that lets Claude connect to the systems a commercial real estate team already runs: deal files and data rooms, property management exports like T-12s and rent rolls, email and calendar, and internal market data. Instead of pasting documents into a chat, Claude reads the live source, and the citation trail points back at your system of record. Every connection is permissioned per tool, so your firm decides exactly what Claude can see. PSV builds CRE AI on Claude by Anthropic, and MCP is the plumbing that grounds those answers in a firm's actual data.
What MCP connects
Claude, plugged into the tools you already run
Four categories cover most of what a CRE team touches in a week. Each one is a connection your firm turns on deliberately, and can turn off the same way.
Deal files and data rooms
The folders where deals actually live: OMs, leases, closing docs. Claude reads the file in place and cites the page it pulled from.
Property management exports
T-12s, rent rolls, budget files. Claude abstracts them straight from the export, each line traceable to its source row.
Email and calendar
Deal threads, broker correspondence, tour schedules. Claude summarizes, drafts, and checks commitments against the calendar you actually keep.
Market data
Internal comps, deal flow trackers, research files. Claude answers from your data set instead of a general guess.
Without MCP
You export, copy, and paste documents into a chat. Answers are only as current as the last paste, and checking a number means finding the file again.
With MCP
Claude reads the live source, and the citation trail points at your system of record. Verifying a number is one click, not a search.
The grounding matters more than the model brand, which is the case our Claude vs ChatGPT comparison makes in full. MCP is how the grounding stops being manual.
A sensible order
What a CRE shop should connect first
Three steps, in this order. Each one earns the trust that makes the next one an easy conversation.
- 01
Files first
Deal folders and document libraries. This is the largest early payoff: Claude answering from the real OM, rent roll, and T-12 instead of a paste.
- 02
Then email and calendar
Once file answers are trusted, connect correspondence. Deal threads, follow-ups, and scheduling stop being copy-paste jobs.
- 03
Then internal data
Comps, deal flow, portfolio exports. The highest-value connection, and the one that most deserves a deliberate, reviewed rollout.
Bring IT and security into the loop from the first connector. Access is permissioned per tool and revocable, and a rollout that starts with review moves faster than one that has to backtrack.
How teams get connected
Off the shelf first, engineering when it counts
Most of what a CRE team wants connected needs no code at all. The exceptions are worth knowing before anyone scopes a project.
Off-the-shelf connectors
Connectors already exist for the common ground of CRE work: the document libraries, inboxes, calendars, and spreadsheet files most shops run on. Turning one on is a settings task, not a build.
Custom connections
Internal databases and proprietary systems need a purpose-built MCP server. That is an engineering task, and the kind PSV builds for firms.
Why the Company Brain matters here
MCP reaches the file. Your firm decides what it means.
Turning a connection on is the solvable half. The harder half is that your firm's way of reading a deal does not arrive with it, and no team wants to move its whole day into a new application to get that. So the standard your firm works to has to meet people where they already are: the inbox, the spreadsheet, the chat window that is already open. That is the half PSV builds.
Nobody has to move into a new application to get it.
The inbox, the spreadsheet, and the file share your team already opens stay where the work happens. Answers arrive there already reflecting how your firm works, so there is no second system anyone has to remember to open.
Rollout does not become a change-management project.
The screens people use are the screens they used last week. Nothing to migrate, no parallel system to run for a quarter, no holdouts to win over. The thing anyone actually notices is that the work comes back better.
It reaches the people who would never open a new tool.
The partner who lives in email and the analyst who lives in a model both work to the same firm standard without changing a habit. The benefit stops being limited to whoever is willing to learn something new.
Frequently asked
MCP for CRE, answered
- What is MCP in commercial real estate terms?
- MCP (Model Context Protocol) is the open standard that lets an AI assistant like Claude connect to the systems a business already runs. For a CRE team, that means Claude can read deal files, property management exports, and email directly instead of relying on pasted excerpts, so answers stay grounded in the system of record.
- How do I connect Claude to my real estate files?
- For common tools like document libraries, email, and calendars, off-the-shelf connectors already exist: you enable the connection, grant scoped access, and Claude can read what you permit. No code is required for the standard cases. The CRE AI Institute teaches a working setup on real practice deal files.
- Does MCP give Claude access to everything in my systems?
- No. Every MCP connection is permissioned per tool, access is scoped to what your team explicitly grants, and it can be revoked. IT and security review belong in the rollout from the first connector, not after.
- Can Claude read a T-12 or rent roll through MCP?
- Yes, once the folder holding your property management exports is connected, Claude can read the T-12 or rent roll file in place, abstract it into your template, and cite the row behind each figure. The verification step stays with a person before any number is relied on.
- What should a CRE firm connect to Claude first?
- Files first: the deal folders where OMs, rent rolls, and T-12s live, because grounded document answers are the largest early payoff. Email and calendar come next, then internal data like comps and pipeline. Each step should pass IT review before the next begins.
- Do I need a developer to use MCP?
- Not to start. Off-the-shelf connectors cover the common tools, and enabling one is closer to a settings change than a software project. Custom connections to internal or proprietary systems are an engineering task, which PSV handles for firms.
Where to go next
Learn a working MCP setup
The CRE AI Institute, by PSV, teaches a connected Claude setup on real practice deal files: connect, ask, verify the citation. 7-day free trial, $0 today.
Keep reading
The workflow
Claude for real estate underwriting
What a connected setup actually does to an OM, a rent roll, and a T-12.
For builders
Claude Code for CRE
Where a CRE team crosses from turning connectors on to building its own.
CRE AI Institute
CRE AI training
Connect, ask, verify the citation, taught step by step on a real practice deal.
Connector notes · PSV newsletter
What CRE teams connected, and what changed the week after.
Which system a firm wired up first, what its analysts stopped doing by hand, and the connections that turned out not to be worth the review they needed. Written for the person who has to get IT to say yes. Free, and one click to leave.
No spam. Unsubscribe in one click.
Next step
See what your firm should connect first.
Ten minutes. An honest read on where you stand, the highest-value opportunities, and which engagement fits, if any.