Malaysia: JUPEM land lots and PLANMalaysia local-plan zoning

Settings → Connectors → Add custom connector, paste the URL, then Connect and sign in with Google.

Settings → Apps & Connectors → Advanced → Developer mode, then Create with the URL and OAuth authentication.

in ~/.cursor/mcp.json

Find Malaysian land lots (JUPEM cadastre) by UPI, lot number or location. query takes a UPI (e.g. 1601400113193; dots, dashes and spaces allowed), a lot number ('Lot 3193', 'PT 1234') with negeri and optionally daerah, mukim and seksyen codes to narrow it, or coordinates as 'latitude, longitude' (e.g. 2.9264, 101.6964). With coordinates it returns the lots containing the point (distance 0), then the nearest within `radius` metres, closest first. To search an address, geocode it first; a radius of 25–100 m helps with geocoded points. Lots are only loaded for some states so far, so no result may just mean the state isn't loaded. Each lot has id (the UPI), negeri and negeriName, daerah, mukim (and mukimName where known), seksyen, lot, keluasan (m²) and bbox. Use MY_lot_get with an id for zoning and the boundary.

One Malaysian lot by UPI (id from MY_lot_search): negeri, daerah, mukim, seksyen and lot, keluasan (area recorded by JUPEM, m²), and zona, the local-plan zones covering it, largest share first: gunatanah (land use, Malay) with gunatanahEn (English), status (Sediada existing, Komited committed, Cadangan proposed) and share of the lot (0–1). Zones covering under 5% of the lot are left out, since zone and lot boundaries come from different surveys; empty zona means no local plan is loaded there. Set include_geometry for the boundary as GeoJSON.

Local-plan land-use zoning (Rancangan Tempatan, PLANMalaysia) at a location in Malaysia, or one zone by id. Pass query as 'latitude, longitude' (e.g. 1.4927, 103.7414), or id. Each zone has id, negeri and negeriName, gunatanah (land use in Malay: Perumahan, Komersial, Industri, Pertanian, …) with gunatanahEn (English), kod (land-use code: class prefix + sub-class digits, e.g. TRM203 housing, PT103 farming), status (Sediada existing, Komited committed: approved but not built, Cadangan proposed by the plan), rancangan (the local plan, e.g. 'RT Daerah Kota Tinggi'), pbt (local authority), tahun (data year), luasHektar (zone area recorded in the plan, hectares), and lot, daerah, mukim and seksyen as the plan writes them (names or bare numbers, not codes). Empty fields are left out. Zoning is loaded for some states only; an empty result means no plan is loaded there, not that the land is unzoned. Where plans overlap, more than one zone is returned, smallest first.

A map image centred on a Malaysian lot (id, the UPI from MY_lot_search) or a point (query), with every lot in view outlined and labelled with its lot number, so you can see which lot is where. The lot passed as id is drawn in red with a larger label; a query point is a red dot. Returns the lots in view as JSON (label: the lot number, with /2 on a number repeated from another mukim or section; id (UPI), lot, keluasan in m²; labelled: false where its label didn't fit), then one JPEG per basemap. Basemaps: satellite (Esri World Imagery, often a few years old), hybrid (the same imagery with road and place names), streets and topo (Esri's street and topographic maps). Pass several to compare, e.g. ['satellite', 'streets'] to match buildings with street names. Lot outlines are yellow on imagery and magenta on maps. Lots are only loaded for some states, so elsewhere the image has none. Imagery is not always aligned with the cadastre: offsets of a few metres are possible. A scale bar is at bottom left. Labels are left off where they'd overlap; call again with a smaller radius to read them. Each image costs about as much context as 1,000 words, so ask for what you need.