Skip to main content

MCP Server

DealMachine runs a remote MCP server at:
Use it when an AI agent needs live property intelligence, owner contact data, comps, property and people search, exports, account usage, or location lookup.

Authentication

MCP clients authenticate with a DealMachine API key in the Authorization header:
Get an API key from Developer Settings. OAuth-aware MCP clients can also discover authorization metadata from:

Connect Claude Code

Connect Claude Desktop

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json:

Connect Cursor

Add this to .cursor/mcp.json:

Direct HTTP Check

MCP Tools

DealMachine currently exposes 21 MCP Tools.

Enrichment

Search, Export, Comps, And Locations

Discovery And Account

Address autocomplete is intentionally not exposed as an MCP Tool. Use dealmachine_location_search to normalize a city, county, state, or ZIP, and use dealmachine_enrich_address for a property address.

Parameters Added Across MCP Tools

Phone output types use wireless, landline, voip, or unknown. dealmachine_enrich_name estimates include associated property totals and page-aware property credits when both estimate_cost=true and include_properties=true are passed.

Credit-Safe Agent Defaults

  • Call dealmachine_filters and dealmachine_fields before constructing searches.
  • Call dealmachine_property_count or dealmachine_people_count before any large search or export.
  • Call dealmachine_usage before batch work.
  • Use contact_audience: "none" for property lookup or enrichment when contacts are not needed.
  • Confirm with the user before exporting or returning a large credit-consuming result set.
  • Default property exports to owner contact rows unless the user explicitly asks for property-only rows.