Public dataConnector
Urbanisme
PLU/GPU zoning, QPV status and commune demographics for any French parcel, read live from open government data in Claude or ChatGPT through Tulina's MCP server.
What it can do
2 read
- 01Read
Read PLU/GPU zoning for a parcel
- 02Read
Read QPV and priority-funding zone status, and commune-level demographics
Open data: no credential to issue, hold or revoke. It reads the same source a person could look up by hand, at a scale nobody has time to do by hand.
Is there an MCP server for French zoning and PLU data?
This one, and it needs nothing installed or hosted separately — it already runs through Tulina's own MCP server, the same session as Claude or ChatGPT. A hosted MCP server exists elsewhere for cadastre parcels and PLU zoning alone; this reads that same zoning plus the layers a screening or funding-eligibility check also needs — QPV and priority-funding zone status, commune-level demographics — from data.gouv.fr, with no separate connector to configure.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Urbanisme once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Urbanisme at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Urbanisme returns something usable instead of something generic.
Processes that run on Urbanisme
None published yet.