ukplanning_search
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_search for the schema, then POST the same URL with its arguments for the data.
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 ignored upstream and returns the whole 25-million-row platform, so this tool does not accept one. To find a designation by place, use ukplanning_entities_at_point instead. Use this for “list the conservation areas published by organisation X”, “which entity has reference CA18”, “how many brownfield-land records exist”. Example: ukplanning_search({ dataset: “conservation-area”, reference: “CA18” })
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
dataset | string | no | Dataset slug from ukplanning_datasets, e.g. “conservation-area”, “listed-building”, “green-belt” |
typology | string | no | Typology filter, e.g. “geography”, “category”, “organisation” |
reference | string | no | The publisher’s own reference for the entity, e.g. “CA18”. NOT unique across councils — pair with organisation_entity |
curie | string | no | Prefixed reference in “prefix:reference” form, e.g. “conservation-area:CA18” |
organisation_entity | number | no | Entity id of the publishing organisation (a local planning authority), e.g. 278 |
entry_date_year | number | no | Restrict to records first entered in this year, e.g. 2026 |
limit | number | no | Maximum rows to return (default 25, max 100) |
offset | number | no | Row offset for paging (default 0) |
include_geometry | boolean | no | Include the full WKT boundary of each row (default false) |
Example call
Arguments
{
"dataset": "conservation-area",
"reference": "CA18",
"limit": 3
}
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_search","arguments":{"dataset":"conservation-area","reference":"CA18","limit":3}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('ukplanning_search', {
"dataset": "conservation-area",
"reference": "CA18",
"limit": 3
});
More examples
{
"curie": "conservation-area:CA18",
"limit": 3
}
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.