Titleman connector
Titleman is an AI analyst for commercial real estate. This connector puts it inside the assistant you already use: you ask for a BOV, comparables or an underwriting by address, Titleman runs it, and the finished report comes back in the conversation. It speaks the Model Context Protocol, so the same server works for Claude, ChatGPT and any other MCP client.
What you need
- A Titleman account — sign up here. The connector runs reports as you, against your own workspace.
- An assistant that supports remote MCP servers (Claude on web, desktop or Claude Code; ChatGPT with apps enabled).
Running a report consumes Titleman credits, exactly as it does in the web app. The read-only tools below are free.
Connect it
- In your assistant, open its connector settings and choose to add a custom or remote MCP server.
- Paste the server URL:
https://titleman.ai/_mcp/titleman - Your browser opens titleman.ai and asks you to sign in (or to create an account if you don't have one yet), then shows exactly what the assistant is asking for. Approve it.
- You land back in the assistant with the connector live. Ask it something — "Ask Titleman for a BOV on 1101 N Arthur Ashe Blvd, Richmond VA" — and it will call
create_bov, then poll until the report is ready.
How it authenticates
OAuth 2.1 with PKCE (S256) — no keys to copy, nothing to paste. The server publishes standard discovery documents, so a compliant client finds everything on its own:
/.well-known/oauth-authorization-server/.well-known/oauth-protected-resource/_mcp/titleman
A client identifies itself in whichever of the three ways it prefers:
- Client ID Metadata Document — the
client_idis an https URL serving the client's own metadata, which we fetch and validate. Nothing is registered, and this is the mode Claude recommends. - Dynamic client registration (RFC 7591) at
/oauth/register. Clients register as public by default and are held up by PKCE alone. - Confidential registration, for clients that require a secret at the token endpoint — ask for
client_secret_postorclient_secret_basicat registration and one is issued. Microsoft 365 agent connectors need this.
PKCE is required of every client, secret or not. OAuth 2.1 and the MCP specification both ask for it, and holding a secret does not buy an exemption from it.
Two scopes are requested: reports (start and read your analyses) and portfolio (list the properties in your workspace). Access tokens last 30 days and refresh silently.
Tools
Read-only
Annotated readOnlyHint: true. They never change anything, so most clients let them run without asking each time.
| Tool | Title | What it returns |
|---|---|---|
list_reports | List recent reports | Your recent analyses: room_id, title, product, state and a link to the full report. |
get_report | Get a finished report | One report by room_id, with its saved versions. |
get_report_status | Check report status | Where a running analysis has got to. |
list_properties | List portfolio properties | The properties in your Titleman portfolio. |
get_property | Get a portfolio property | One property you own: address, asset type, units, lease count. |
Write
These start a real analysis and spend credits. They are asynchronous: each returns a room_id immediately, and the assistant polls get_report_status before reading the result. None of them delete or overwrite anything.
| Tool | Title | What it starts |
|---|---|---|
create_bov | Start BOV (Broker Opinion of Value) report | A value opinion for one address. |
create_comps | Start comparables (COMPS) report | Comparable properties on the market now, with asking terms. |
create_underwriting | Start underwriting analysis | Income, expenses, debt, IRR and sensitivity. |
create_best_use | Start highest-and-best-use analysis | What a site you already own should become. |
create_buyer_list | Start buyer list analysis | The ranked universe of likely buyers for an asset. |
create_dd | Start title & legal due diligence | Title, ownership chain and encumbrances on the property itself. |
find_properties | Find properties matching criteria | A shortlist of specific buildings in a place, from free-text criteria. |
What the connector can and cannot see
- Every tool is scoped to the account that approved it. It reads your reports and your portfolio, and nothing belonging to anyone else.
- It does not read your conversation history, your assistant's memory, or files you have not passed to a tool.
- It moves no money and makes no purchases.
- Report content is stored in your Titleman workspace exactly as if you had run it in the web app, under the Privacy Policy and the Data Processing Addendum.
Revoke access
Open titleman.ai/mcp and press Revoke. That cuts off every grant and every token the account holds at once, server-side and immediately — not merely letting them expire — so it works even though the assistant never showed you a token to hand back. Removing the connector on the assistant's side stops that assistant using it, but only Revoke ends the grant here.
Support
- Questions and problems: [email protected]
- Privacy and data requests: [email protected]
- Privacy Policy · Terms & Conditions · Security Addendum
Titleman is not a broker, appraiser or law firm. Outputs are drafts for a licensed professional to review and sign.