Miami-Dade FL Property Appraiser MCP Server

What does Miami-Dade Property Appraiser MCP Server do?

Miami-Dade Property Appraiser MCP Server gives AI agents live access to Miami-Dade County, Florida real estate records through the Model Context Protocol, by talking directly to the same public JSON API that powers the county's Property Search web app. It covers every search form on that app — address, owner name, subdivision name, and folio number — plus the full property record card (ownership, assessed/taxable values by year, exemptions, land and building details, extra features, and complete sales history) for any folio.

Because it runs on Apify, the server is always on (Standby mode), scales automatically, and is billed per tool call with no infrastructure to manage.

Why use Miami-Dade Property Appraiser MCP Server?

• Due diligence & underwriting — pull ownership, assessed value trends, and sales history for a parcel before making an offer.
• Market research — sweep a subdivision or neighborhood for comparable sales and assessment values.
• Skip tracing / owner lookups — find every parcel tied to an owner name.
• Tax & exemption audits — check homestead and other benefit/cap values by year for a folio.
• Agent workflows — let an LLM answer "what's this property worth" or "who owns 123 Main St" questions live, without you writing scraping code.

How to use Miami-Dade Property Appraiser MCP Server

1. Deploy this Actor to your Apify account (or run it directly from the Store).

2. Connect your MCP client (Claude Code, Claude Desktop, Cursor, etc.) to the Actor's Standby endpoint:

   $claude mcp add miami-dade-pa --transport http "https://rl1987--miami-dade-fl-mcp-server.apify.actor/mcp" --header "Authorization: Bearer $APIFY_TOKEN"
   

   Swap rl1987 for the Actor owner's Apify username and set $APIFY_TOKEN to your own Apify API token (found in Apify Console → Settings → Integrations) — not the Actor owner's. Add --scope local instead of the default --scope project if you don't want the connection committed to a shared .mcp.json.

3. Verify the connection with claude mcp list (or your client's /mcp command) — you should see 5 tools.

4. Ask your agent to look up a property, e.g. "look up the owner and sales history for folio 01-4137-023-0020" or "find all properties owned by SMITH JOHN in Miami-Dade".

A team can commit a shared .mcp.json (URL only, no token) to a repo; each teammate then runs claude mcp add --scope local once with their own token.

Input

This Actor exposes no batch/dataset input schema — it runs in Standby mode as a live MCP server. All configuration happens per tool call, driven by your MCP client / LLM. See Tools below for each tool's parameters.

Tools

Tool	Mirrors	Parameters	Returns
search_by_address	ADDRESS tab	address, unit (optional), offset, limit	Matching properties: folio/strap, owners, site address, subdivision, status
search_by_owner	OWNER NAME tab	owner_name, offset, limit	Same as above, matched by owner name
search_by_subdivision	SUBDIVISION NAME tab	subdivision_name, offset, limit	Same as above, matched by subdivision
search_by_partial_folio	FOLIO tab	partial_folio, offset, limit	Same as above, matched by partial folio
get_property_by_folio	Property Record Card	folio (13 digits, dashes optional)	Full record: ownership, mailing/site address, legal description, assessment & taxable values by year, exemptions/benefits, land, building, extra features, full sales history

Each search tool returns a list of results with a Strap (folio) field — feed that into get_property_by_folio to fetch the complete record for any match.

Output example

{
  "Completed": true,
  "PropertyInfo": {
    "FolioNumber": "01-4137-023-0020",
    "DORDescription": "COUNTY : OFFICE BUILDING",
    "Municipality": "Miami",
    "LotSize": 320035
  },
  "OwnerInfos": [{ "Name": "MIAMI-DADE COUNTY" }],
  "Assessment": {
    "AssessmentInfos": [
      { "Year": 2026, "TotalValue": 102900000, "LandValue": 80008750 }
    ]
  },
  "SalesInfos": []
}

Every tool call returns the raw, structured JSON from the county's own API — no HTML scraping, no data loss from re-formatting.

Known caveat: verified against the live Property Search site, every section matches exactly (assessment, taxable, benefits, legal description, land, building, sales history) except Additionals (GIS-derived land-use flags). Three of its fields — Community Development District, Community Redevelopment Area, Empowerment Zone — can come back as the raw sentinel "COUNTYGIS" instead of the resolved value; on the live site those often resolve to "NONE". The county's own SPA resolves this with extra GIS map-service calls this Actor doesn't replicate. Don't treat "COUNTYGIS" in Additionals as a literal answer for those three fields.

Pricing / Cost estimation

This Actor uses Pay Per Event pricing: a flat fee per completed tool call (see the Actor's Monetization tab for the current price). There's no charge for failed calls or for connecting/idling. A typical due-diligence lookup (one search + one full record fetch) costs two tool-call events.

Tips

• Use search_by_partial_folio for folio-prefix/typeahead-style lookups when you don't have the full 13-digit number.
• offset/limit paginate large result sets (e.g. common owner names or large subdivisions) — default page size is 25.
• Folio numbers work with or without dashes (01-4137-023-0020 or 0141370230020).

FAQ, disclaimers & support

This Actor reads the same public data the Miami-Dade Property Appraiser's own Property Search website serves to any visitor. It is provided for informational purposes; assessment/tax data is continually updated by the county and this Actor may not reflect the very latest roll — always verify against miamidadepa.gov for official purposes. Not affiliated with Miami-Dade County or the Property Appraiser's office.

The county's separate PRC/VAB advanced-search tool (PAOnlineTools/PRC/PRCadvancedSearch.aspx) is a Value Adjustment Board hearing/agenda tool behind bot-mitigation, not a general property search — it is out of scope for this Actor.

Found a bug or want a feature added? Use the Issues tab on this Actor's page.

Resources

• Miami-Dade Property Search
• Model Context Protocol
• FastMCP documentation
• Apify Standby mode