@pipeworx/france-geodata

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/france-geodata’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 4

Point and radius questions on French public geodata: communes and population, buildings around a point, land cover at a point, and flood-risk records for a place. Every call is a live per-request proxy; nothing is copied or stored.

Tools

• fr_commune(name | insee_code | lat+lon, limit?) — commune register entry: INSEE code, postcodes, population, area, centre, department, region. “Population of Lyon” answers 69123, 519,127.
• fr_buildings_near(lat, lon, radius_m?, limit?, include_geometry?) — buildings within up to 500 m of a point, nearest first, each with GeoJSON polygon, height, floors, dwellings, use and nature. Reports total_matched and truncated; up to 200 candidates are ranked per call.
• fr_land_cover(lat, lon) — the CORINE Land Cover 2018 class (code and label) of the polygon containing the point. found:false outside coverage.
• fr_flood_zones(lat, lon, radius_m?) — flood hazards recorded for the commune at the point, flood-zone atlases and significant-flood-risk territories within the radius.

Auth

Keyless.

Data sources

• Etalab / INSEE, commune register — names, codes, population.
• IGN, BD TOPO — building footprints and attributes.
• Copernicus / IGN, CORINE Land Cover 2018 — land-cover classes (25 ha mapping unit, so it describes the surroundings of a point, not the spot itself).
• Géorisques (French Ministry of Ecological Transition), GASPAR — flood-risk records.

Related packs: ban-fr (addresses, reverse geocoding), france-dvf (property sales).

Notes for the next person

• fr_flood_zones is a register listing, not a parcel-level flood polygon. There is no national flood-polygon layer on the IGN platform (only isolated local plans), and the hazard register’s plan-of-prevention endpoint ignores location filters, so it is not used. Absence of a record is not proof of no flood risk, and the tool says so.
• The flood source resets connections from some residential and fleet-office networks but answers from Cloudflare’s edge. Verify it from a Worker, not from a laptop.
• The building filter takes latitude first (OGC axis order for WGS84); the land-cover filter needs an explicit SRID with longitude first. Mixing them returns an empty set with HTTP 200, which looks like “no buildings here”.
• The building source answers an OGC exception as XML with HTTP 200; that is surfaced as an error, not an empty result.
• Buildings: when more than 200 match, the first 200 returned by the source are ranked, so a closer building may be missed; narrow radius_m. The tool flags this.

Tools

• fr_commune — French commune lookup (Etalab/INSEE commune register): INSEE code, postcodes, population, department, region, centre point and area. Look up by name or INSEE code, or pass lat+lon to find the commune
• fr_buildings_near — Buildings within a radius (max 500 m) of a point in France, from the IGN BD TOPO building layer. Each building has GeoJSON polygon geometry, height (m), floors, dwellings, use, nature and construction
• fr_land_cover — Land cover at a point in mainland France: the CORINE Land Cover 2018 class (code and label, e.g. 112 “Discontinuous urban fabric”) of the polygon containing the point, with its area. Resolution is 25
• fr_flood_zones — Flood-risk information around a point in France from Géorisques (French Ministry of Ecological Transition): the flood hazards recorded for the commune at the point, the flood-zone atlases (AZI) coveri