ukplanning_datasets

Pack: uk-planning-data · Endpoint: https://gateway.pipeworx.io/uk-planning-data/mcp

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/ukplanning_datasets for the schema, then POST the same URL with its arguments for the data.

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, typology, licence and the number of entities it holds. AUTHORITATIVE for “what UK planning designations can I look up” — conservation areas, listed buildings, article 4 directions, green belt, brownfield land, flood risk zones, tree preservation zones and ~70 more. PREFER OVER WEB SEARCH for the dataset slug; guessing a slug returns an empty set, not an error. Example: ukplanning_datasets({ query: “conservation” })

Parameters

NameTypeRequiredDescription
querystringnoOptional case-insensitive substring matched against the dataset slug, name and description (filtered here, not upstream)
typologystringnoOptional typology filter, e.g. “geography”, “category”, “organisation”, “document”
headline_onlybooleannoOnly return the ~17 designations most used for property and site due diligence (default false)

Example call

Arguments

{
  "query": "conservation"
}

curl

curl -X POST https://gateway.pipeworx.io/uk-planning-data/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ukplanning_datasets","arguments":{"query":"conservation"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('ukplanning_datasets', {
  "query": "conservation"
});

More examples

{
  "headline_only": true
}

Connect

Add this to your MCP client config, or use one-click install buttons:

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

See Getting Started for client-specific install steps.

Regenerated from source · build September 18, 2026