All news
Integration4/25/26Product

DealDesk on Claude, connect the MCP and pull deals into chat.

An OAuth flow, a sidebar in Claude Desktop, and your deal pipeline becomes part of the conversation. No copy-pasting between apps.

DealDesk is now live as a Claude connector. That sentence is short and the implication is large, so let's unpack what it means.

What an MCP connector actually does

Model Context Protocol, the open spec Anthropic shipped at the end of 2024, lets a Claude assistant read from and write to outside systems through a controlled set of tools. Once DealDesk is connected to your Claude account, the assistant can see your deal pipeline, your abstracts, your LOIs, your comps. It can also act on them: update a deal stage, save a comp, generate a counter-LOI in your firm's house style.

The user experience is just chat. You're sitting in Claude Desktop and you say "draft a counter LOI for the 1500 Market deal." Claude pulls the deal record from DealDesk, reads the lease abstract, references the firm's LOI template, drafts the counter, and either writes it back into the deal as a draft or hands you the text. No app-switching. No copy-pasting between tools.

Why this is the natural distribution

Brokers spend a lot of time in chat now. Most of the working tenant reps we talk to have Claude or ChatGPT open as a side panel, and they ask it to draft emails, summarize market research, and run quick comparisons. That's the existing surface where AI has already won the broker's attention.

The losing strategy for a CRE software vendor is to ignore that surface and try to build a parallel "chat with our app" feature inside their own UI. The winning strategy is to make sure that when the broker is in Claude, which they will be regardless, your data and your tools are right there.

MCP is the cleanest way to do that. The connector is a server-side integration; the broker doesn't install anything except their existing Claude client; the auth flow is OAuth standard; the data stays in DealDesk's database with our existing permissions model. We don't ship the broker's deals to Anthropic and we don't store their Claude prompts. The Claude assistant just gets scoped read/write access to the deals the user is allowed to see.

What you can do with it today

  • Open and close deals ("mark the Bonsai deal as Closed")
  • Pull abstracts and LOIs into the conversation for review
  • Draft new LOIs and counter-LOIs grounded in pipeline data
  • Run comp searches across your firm's saved deals
  • Generate space reports from a list of CoStar URLs
  • Update deal stages, owners, next-action notes

The thing that's not yet in the connector but is on the roadmap: bulk operations. We don't yet support "abstract these 14 leases I just dropped into my inbox" through the MCP, that still happens via the DealDesk web app. We expect that to ship in the next four-to-six weeks.

How to set it up

If you have a DealDesk Pro account, the connector is in your settings panel under Integrations → Claude. The setup is a single OAuth flow; you'll be back in your conversation in about 60 seconds. If you don't yet have an account, the free tier supports the read-only side of the connector, you can ask Claude about deals you've added but you'll need Pro to write back into them.

More reading

See it on a real lease.

Free tier is three abstracts a month, no card. Drop in a lease your team has already done by hand and check the diff.