Uk Planning Data MCP server

@pipeworx/uk-planning-data

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.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

catalogue: the slug you pass to every other tool, plus row counts and licence.

• ukplanningdatasets(query?, typology?, headlineonly?) — the dataset

— every designation whose boundary covers one lat/lon. The site due-diligence call: "is this address in a conservation area / green belt / flood zone".

• ukplanningentitiesatpoint(latitude, longitude, dataset?, limit?, includegeometry?)

— filter entities. Deliberately takes NO free-text query; see below.

• ukplanningsearch(dataset?, typology?, reference?, curie?, organisationentity?, entrydateyear?, limit?, offset?, include_geometry?)

• ukplanningentity(entity, includegeometry?) — one entity by numeric id.

Auth

Keyless.

Data sources

• — the dataset catalogue.
• — entity search and point lookup.
• — one entity.
• — the parameter list.

Things worth knowing:

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 ukplanningentitiesatpoint to search by place, and dataset/curie/reference/organisationentity to filter. Those four genuinely filter (verified: reference=CA18 → 31 rows).

• q is documented and does nothing. ?q=Trafalgar%20Square&limit=3

conservation area can be 60 KB. Every list call here sends excludefield=geometry&excludefield=point unless the caller asks for it.

• Geometry is enormous. Each row carries a WKT MULTIPOLYGON; one

defaults to intersects. Omit dataset to get every layer at once.

• Point lookup needs no relation parameter — ?longitude=&latitude=

31 councils. Pair it with organisation_entity, or use the prefix:reference curie.

• reference is not unique. It is the publisher's own id, so "CA18" matches

(entry-date in the body, entrydateyear in the query). Both are upstream's.

• Response fields are hyphenated, query parameters are underscored

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "uk-planning-data": {
      "url": "https://gateway.pipeworx.io/uk-planning-data/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/uk-planning-data/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Shortened. The full README is on GitHub.