Multi-Surface Agentic Analysis for Commercial Real Estate
Valuation workstreams were trapped in one interface, so analysts could not run the same agentic analysis from the tools they already used — Slack, a custom UI, or Claude Desktop.
The Problem
Commercial real estate valuation is a repeatable workstream — pull comps, assemble financials, run the model, write the brief — but the work lived in whichever app someone happened to have open. A custom analysis UI, Slack, and Claude Desktop each needed the same capabilities. Duplicating that logic per surface would drift immediately. I designed a single agentic layer that any of those clients could call.
The Architecture
flowchart TB
subgraph surfaces [Client Surfaces]
UI[Custom Analysis UI]
Slack[Slack]
Claude[Claude Desktop]
Other[Other MCP Clients]
end
subgraph mcp [Centralized MCP Server]
Tools[Valuation Tools]
Context[Shared Context]
Workflows[Workstream Orchestration]
end
subgraph resources [CRE Resources]
Comps[(Comps and Market Data)]
Financials[(Asset Financials)]
Models[Valuation Models]
end
subgraph output [Valuation Output]
Memo[Analysis Memo]
Numbers[Valuation Package]
end
UI --> mcp
Slack --> mcp
Claude --> mcp
Other --> mcp
Tools --> Comps
Tools --> Financials
Tools --> Models
Workflows --> Tools
Context --> Workflows
Workflows --> Memo
Workflows --> Numbers One Server, Many Surfaces
The MCP server is the product. Clients do not own the valuation logic; they call it.
- Custom UI: A purpose-built analysis surface for longer valuation sessions
- Slack: Kick off or continue a workstream from the thread where the deal is already being discussed
- Claude Desktop: Same tools, in a desktop agent that already has the analyst’s local context
- Anything else that speaks MCP: New surfaces attach without rewriting the workstreams
Because the tools and orchestration live in one place, a valuation started in Slack can be inspected in the UI, and a Claude Desktop session uses the same comps, financials, and models.
Tech Stack
- MCP — Centralized tool and workstream server
- Multi-surface clients — Custom UI, Slack, Claude Desktop
- Valuation workstreams — Comps, financials, and model runs as callable tools
The Impact
Analysts run the same CRE valuation workstreams from whichever surface they are already in. The MCP server is the contract: add a client, keep the analysis.