How-to

Run Titleman from inside Claude

Connect Titleman to Claude over MCP: mint a token, start six job types by address, find properties, and read reports back — plus an honest list of what the connector cannot do yet.

Mint your connector token

Titleman exposes an MCP server, so you can start jobs and read results without leaving your assistant. Claude is the connector that is live today — that is the whole list, and we would rather say it than show a wall of logos for things that do not exist.

Connecting

The connector card lives on MCP. It mints your Connector URL and the same card revokes and regenerates it.

The four steps shown on the MCP page: open claude.ai Settings then Connectors, add a custom connector and paste the Connector URL, authorize with your Titleman access token, then ask Claude in any chat

Every call is authenticated as you, and every tool is scoped to your account — your rooms, your properties, your reports, and nothing else.

⚠ One of the example prompts on that card asks for comps in Dubai Marina. The connector will happily accept it; our coverage will not reward it. We hold no register outside the United States, Spain, Germany and France, and outside those a request comes back thin rather than refused — read Coverage and data before you automate anything against a market. This applies to every tool below.

What you can start from Claude

Six job types, each from a full street address:

ToolStarts
create_bovA broker's opinion of value
create_compsA comparables board
create_underwritingIncome, debt, returns, scenarios
create_best_useHighest-and-best-use scenarios
create_ddA diligence pass
create_buyer_listA ranked buyer pool

Finding and reading back

ToolDoes
find_propertiesSearch in words — location, type, count, price range, size
list_properties / get_propertyYour portfolio, then one property in full
list_reportsYour reports
get_report_statusWhether a run has finished, by the room_id the create call returned
get_reportThe finished report

The pattern is: create returns a room_id, you poll get_report_status with it, then get_report. Runs take minutes to hours depending on the product — Choosing a product has the measured times — so treat it as asynchronous, not as a request that blocks.

What the connector cannot start

Value Opinion, Scout, Feasibility, Excels and Legal are not exposed over MCP. If your job is one of those, run it in the product. This is a real gap rather than an oversight worth hiding: the connector covers six of the eleven things we do.

One caveat on the sixth: Buyer List runs, and almost nobody outside the company has used it — one client run in the last thirty days. It is there and it is not proven.

What is not available yet at all

The Connectors page lists these honestly, and so will we: an Excel add-in, email inflow (a forwarding address per workspace), Dropbox folder sync, and a property management system pull for rent rolls and T-12s. A Lease Comps Feed is marked coming soon, and Marketplace Data is a conversation rather than a switch.

None of them is live. If one of them is what would make Titleman work for your firm, say so — that is useful to us and it is a straight answer either way.

Before you build on it

Anything you automate through the connector inherits every limit the products have: coverage stops where our registers stop, local planning and tax rules are not applied, and the outputs are what What you get back says they are. A script that assumes a deck or a PDF will come back will be wrong most of the time.

Mint your connector token

Bring us a deal you already closed

We run it through Titleman and show your team the finished work next to their own.