← All BumiAtlas MCP endpoints

BumiAtlas MCP

Netherlands: Kadaster parcels by kadastrale aanduiding

Dutch cadastral parcels from the Kadaster's BRK Kadastrale Kaart, as tools an AI assistant can call: find a parcel by cadastral municipality, section and number or by coordinates, read its registered size, 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/netherlands

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-netherlands https://bumiatlas.com/mcp/netherlands
ChatGPT
Settings → Apps & Connectors → Advanced → Developer mode, then Create with the URL and OAuth authentication.
Cursor
in ~/.cursor/mcp.json
{
  "mcpServers": {
    "bumiatlas-netherlands": {
      "url": "https://bumiatlas.com/mcp/netherlands"
    }
  }
}

Tools

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

NL_parcel_search
Find Dutch cadastral parcels (Kadaster BRK) by kadastrale aanduiding, id or location, with each parcel's whole record. query takes a cadastral municipality (name or AKR code), section and number ('HVS00 A 1234', 'Hilversum A 1234'), a municipality and section ('Hilversum A', lists the section's parcels, paged with offset), coordinates as 'latitude, longitude' (e.g. 52.3731, 4.8922), or a parcel id ('NL.IMKAD.KadastraalObject.76869982570000'). With coordinates it returns parcels containing the point (distance 0), then the nearest within `radius` metres, closest first. Each parcel has id, aanduiding, gemeente (cadastral municipality), gemeenteCode, akrCode, akrName, section, number, volgnummer, area (m²), sizeKind, status, valid, mapArea and bbox. Set include_geometry for each boundary as GeoJSON (keep limit small). Use NL_parcel_image to see a parcel and its neighbours.
query*string
'HVS00 A 1234', 'Hilversum A 1234', 'Hilversum A', 'latitude, longitude', or a parcel id
radiusnumber
Search radius in metres around coordinates(default 25)
limitinteger
Maximum results(default 20)
offsetinteger
Skip this many matches of a number or name search, to page through them(default 0)
include_geometryboolean
Include each boundary as a GeoJSON MultiPolygon(default false)
NL_parcel_image
A map image centred on a Dutch parcel (id, from NL_parcel_search) or a point (query), with every parcel in view outlined and labelled with its section and number, 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, aanduiding, 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 metre or two 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
Parcel id (NL.IMKAD.KadastraalObject.…), 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