Daleads MCP server

DA Leads MCP

<!-- mcp-name: io.github.resuly/daleads-mcp -->

DA Leads MCP lets Claude, Cursor and other MCP clients query Australian development applications and address-level property intelligence through the DA Leads API.

It exposes 36 tools for DA search, canonical project search and monitoring, nearby applications/projects, council and category lookups, read-only SQL analysis, generic entitlement-filtered property intelligence, the closed public Full Property contract, focused Noise, Flood, Bushfire and Walkability screening, score-free Property Core, Suburb Signals, SA2 scenarios, Neighbourhood Context, Solar Resource, keyless samples and sandbox addresses.

Install

Run without installing globally:

uvx daleads-mcp

Or install with pipx:

pipx install daleads-mcp
daleads-mcp

Configuration

Paid tools use a DA Leads API key. The property sample tools work without a key.

{
  "mcpServers": {
    "da-leads": {
      "command": "uvx",
      "args": ["daleads-mcp"],
      "env": {
        "DALEADS_API_KEY": "dk_live_xxx"
      }
    }
  }
}

DALEADSAPIKEY is the only environment variable read by this package. Treat it as a secret. It is sent only to the fixed official HTTPS API endpoint at https://daleads.com.au/api.

For Claude Code 2.1+, add the stdio server to the current project with:

claude mcp add --scope project da-leads -- uvx daleads-mcp

Keyless sample tools work immediately. For paid tools, launch Claude Code from an environment that already provides DALEADSAPIKEY; do not commit a real key to the project MCP configuration.

Official Skills

The 10 canonical Agent Skills live in skills/. A repository checkout exposes the same files to Codex through .agents/skills/ and to Claude Code through .claude/skills/; both directories are thin relative symlinks, so there is only one maintained instruction source. The Skills guide agents through subject identity, coverage, attribution and product-specific limits. They do not grant an API entitlement or expand data rights.

Tools

Development applications

searchdas — Search Australian development applications with filters, newest first. Parameters: state (NSW, VIC, QLD, SA, WA, TAS, NT, ACT), council (full council name, e.g. City of Melbourne), category (trade category, e.g. Renovation / Extension), suburb, postcode, since (ISO date YYYY-MM-DD, lodged on or after), statusgroup (pending, advertised, approved, rejected, other), isresidential (bool), page (default 1), limit (per page, default 20, max 100). Returns {data: [DA record, ...], meta: {total, page, perpage, pages}}. Each record carries id, address, suburb, postcode, council, state, tradecategory, lodgementdate, status, statusgroup, latitude, longitude, infourl and document links; paid plans add description, summary, subcategory, costofdevelopment, decision fields, numberofdwellings, buildingtype, storeys and the full documents list. Applicant names are never returned on any plan.

getda — Retrieve one development application in full. Parameters: daid (integer record id, as returned by searchdas or nearbydas). Returns {data: DA record} with the same field set as above.

nearbydas — Find development applications within a radius of a point, nearest first. Parameters: lat, lng (WGS84 decimal degrees), radiuskm (default 5, max 50), category, since, statusgroup, page, limit (max 100). Returns the same {data, meta} shape as searchdas, with an extra distance_km on each record.

listcategories — List every trade category with its record count, for discovering valid category values. No parameters. Returns {data: [{name, slug, isresidential, record_count}, ...], meta: {total}} — categories such as Renovation / Extension, Swimming Pool / Spa, Granny Flat / Secondary Dwelling and Demolition.

Shortened. The full README is on GitHub.