← All BumiAtlas MCP endpoints

BumiAtlas MCP

Qatar: Ministry of Municipality parcels by PIN and building height

Qatari land parcels from the Ministry of Municipality's cadastre, as tools an AI assistant can call: find a parcel by PIN, zone and block, or coordinates, read its registered area and permitted building height, and see it on a map with its neighbours.

Server URL

Streamable HTTP with OAuth. The first time you connect, your client opens a browser window to sign in with Google; no API key needed.

https://bumiatlas.com/mcp/qatar

Connect

Claude (claude.ai, desktop)
Settings → Connectors → Add custom connector, paste the URL, then Connect and sign in with Google.
Claude Code
claude mcp add --transport http bumiatlas-qatar https://bumiatlas.com/mcp/qatar
ChatGPT
Settings → Apps & Connectors → Advanced → Developer mode, then Create with the URL and OAuth authentication.
Cursor
in ~/.cursor/mcp.json
{
  "mcpServers": {
    "bumiatlas-qatar": {
      "url": "https://bumiatlas.com/mcp/qatar"
    }
  }
}

Tools

Tool names and descriptions are in English, which models understand best; your assistant still answers in your language.

QA_parcel_search
Find Qatari land parcels (Ministry of Municipality cadastre) by PIN, zone and block, or location, with each parcel's whole record. query takes an 8-digit PIN (70155302; an older cadastral key works too), a zone and block ('zone 70 block 15', '70/15', or the QARS reference 7015), a whole zone ('zone 70'), or coordinates as 'latitude, longitude' (e.g. 25.2854, 51.5310). With coordinates it returns parcels containing the point (distance 0), then the nearest within `radius` metres, closest first. A zone or block lists its parcels in PIN order with the total; page with offset. Each parcel has pin, zone, block, buildingHeight (permitted floors, e.g. G+1+P), area (registered, m²), mapArea (m², from the outline), registered (date), ended (cancelled parcels), surveyJob, cdstKey where it differs, and bbox. Set include_geometry for each boundary as GeoJSON (keep limit small). Use QA_parcel_image to see a parcel and its neighbours.
query*string
PIN (8 digits), 'zone 70 block 15', QARS (7015), or 'latitude, longitude'
radiusnumber
Search radius in metres around coordinates(default 25)
limitinteger
Maximum results(default 20)
offsetinteger
Skip this many parcels of a zone or block, to page through them(default 0)
include_geometryboolean
Include each boundary as a GeoJSON MultiPolygon(default false)
QA_parcel_image
A map image centred on a Qatari parcel (id, its 8-digit PIN) or a point (query), with every parcel in view outlined and labelled with its PIN, so you can see which parcel is where. The parcel passed as id is drawn in red with a larger label; a query point is a red dot. Returns the parcels in view as JSON (label, id, pin, buildingHeight, area 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. Parcel outlines are yellow on imagery and magenta on maps. 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.
idstring
PIN (8 digits), drawn in red
querystring
'latitude, longitude' to centre on instead of a parcel
radiusnumber
Metres from the centre to the image edge. Default: fits the parcel with a margin, or 80 m around a point
basemapsarray
One image per basemap(default ["satellite"])
sizeinteger
Image width and height in pixels(default 768)

Try asking

About the data