@pipeworx/uk-planning-data

Connect: https://gateway.pipeworx.io/uk-planning-data/mcp · 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

UK planning designations from planning.data.gov.uk, the MHCLG national planning data platform — look up any point in England and get the conservation areas, listed buildings, article 4 directions, green belt, brownfield land, flood risk zones and tree preservation zones that cover it.

Tools

• ukplanning_datasets(query?, typology?, headline_only?) — the dataset catalogue: the slug you pass to every other tool, plus row counts and licence.
• ukplanning_entities_at_point(latitude, longitude, dataset?, limit?, include_geometry?) — every designation whose boundary covers one lat/lon. The site due-diligence call: “is this address in a conservation area / green belt / flood zone”.
• ukplanning_search(dataset?, typology?, reference?, curie?, organisation_entity?, entry_date_year?, limit?, offset?, include_geometry?) — filter entities. Deliberately takes NO free-text query; see below.
• ukplanning_entity(entity, include_geometry?) — one entity by numeric id.

Auth

Keyless.

Data sources

• https://www.planning.data.gov.uk/dataset.json — the dataset catalogue.
• https://www.planning.data.gov.uk/entity.json — entity search and point lookup.
• https://www.planning.data.gov.uk/entity/{entity}.json — one entity.
• https://www.planning.data.gov.uk/openapi.json — the parameter list.

Things worth knowing:

• q is documented and does nothing. ?q=Trafalgar%20Square&limit=3 returns count: 25355431 — the whole platform — and the same three rows as the unfiltered call. There is no free-text search on this API. This pack does not accept or forward one, because forwarding it returns 25 million rows wearing the shape of a result set. Use ukplanning_entities_at_point to search by place, and dataset/curie/reference/organisation_entity to filter. Those four genuinely filter (verified: reference=CA18 → 31 rows).
• Geometry is enormous. Each row carries a WKT MULTIPOLYGON; one conservation area can be 60 KB. Every list call here sends exclude_field=geometry&exclude_field=point unless the caller asks for it.
• Point lookup needs no relation parameter — ?longitude=&latitude= defaults to intersects. Omit dataset to get every layer at once.
• reference is not unique. It is the publisher’s own id, so “CA18” matches 31 councils. Pair it with organisation_entity, or use the prefix:reference curie.
• Response fields are hyphenated, query parameters are underscored (entry-date in the body, entry_date_year in the query). Both are upstream’s.

Tools

• ukplanning_datasets — List the datasets published on planning.data.gov.uk — the UK government’s national planning data platform (MHCLG). Each row gives the dataset slug you pass to the other tools, its plain-English name,
• ukplanning_entities_at_point — Return every UK planning designation whose boundary covers one latitude/longitude — the single most useful call for site or property due diligence. Answers “is this address in a conservation area / gr
• ukplanning_search — Filter UK planning entities by dataset, typology, publisher reference, curie or publishing organisation. NOTE: planning.data.gov.uk has NO free-text search — its documented q parameter is silently i
• ukplanning_entity — Fetch one UK planning entity by its numeric entity id (from ukplanning_search or ukplanning_entities_at_point). Returns the full record — name, dataset, publisher reference, start/end dates, the publi