Dealflowpro MCP Server

What jbechtel-97/dealflowpro-mcp-server MCP server does

The jbechtel-97/dealflowpro-mcp-server MCP server brings DealFlowPro’s multifamily underwriting calculations into MCP-compatible clients. It is intended for properties with 2 to 200 units and returns common acquisition metrics such as cap rate, DSCR, cash-on-cash return, IRR, and a DFP Score from 0 to 100.

The server also supports offer-pricing analysis. Given target return requirements, it can calculate a maximum offer price and identify the relevant constraint. For an address, it can return flood-zone information, compare neighborhood income with the state median, and report job growth.

How it works

The local package runs as a stdio MCP server and sends tool requests to the DealFlowPro REST API. Every call requires a Bearer API key associated with a DealFlowPro account. The API processes request payloads in memory, and the README states that calls are read-only and idempotent. Results are deterministic for the same inputs, which makes the server suitable for repeatable screening or evaluation fixtures.

The jbechtel-97/dealflowpro-mcp-server MCP server exposes four tools:

• analyze_deal performs a complete analysis, including yearly cash flows, return metrics, DFP Score, and maximum offer price.
• score_deal provides a faster screening result with the DFP Score and key metrics.
• reverse_calc works backward from a target cap rate, cash-on-cash return, DSCR, or IRR to estimate the maximum offer price.
• market_data retrieves selected market indicators for an address.

A hosted MCP endpoint is also available at https://dealflowpro.io/mcp using Streamable HTTP. The repository describes that route as supporting OAuth account sign-in and additional account-scoped tools, while the local npm package provides the four tools listed above.

Setup and configuration

The local server requires Node.js 18 or newer and a DealFlowPro API key. The documented package command is:

npx -y dealflowpro-mcp

Configure the DFP_API_KEY environment variable in the MCP client. Claude Desktop can launch the package with npx and pass the key through its env configuration. Claude Code can add the same command with an environment variable. API keys are obtained from DealFlowPro; the README describes a free five-request key and paid credit or subscription options.

For clients that support remote MCP connections, use the DealFlowPro endpoint instead of running the npm package locally. The remote setup uses a Bearer key for HTTP configurations, while Claude custom connectors can authenticate through OAuth.

Limitations and notes

This server depends on the DealFlowPro API, so API access, account limits, and pricing apply. The documented free allowance is five requests for the lifetime of the key; higher-volume tiers and pay-as-you-go credits are paid. The README lists rate limits by tier and notes that some remote account-management tools are not part of the four-tool local package.

The available market lookup covers the indicators documented by the project: flood zone, neighborhood income relative to the state median, and job growth. The material does not describe broader property-data coverage or guarantee the accuracy of external market information. The project is licensed under MIT.

For developers choosing between local and hosted deployment, the jbechtel-97/dealflowpro-mcp-server MCP server is the local API-key option, while the hosted endpoint is the account-connected alternative.