Skip to content
All engineering use cases

Planning constraints GIS MCP

Overlay planning designations, protected sites and listed assets around a project boundary. Compare listed sources, access requirements and evidence for planning constraints gis mcp.

4 sources · For geospatial data engineers, GIS analysts, planners and ecologists working with agent-assisted queries, web and GIS developers. Enrichment describes potential applications; review source evidence and limitations.

Layer coverage and update cycles differ; confirm constraints with the responsible authority.

Discover sources with MCP

Add this server to an HTTP-compatible MCP client, then call get_source to inspect the first source. The tool call is shown separately from the client configuration. Review upstream access details before requesting data.

{
  "mcpServers": {
    "terramcp": {
      "url": "https://terramcp.earth/mcp"
    }
  }
}

// After connecting, call this discovery tool:
{
  "name": "get_source",
  "arguments": {
    "slug": "planning-data-gov-uk"
  }
}

Listed sources

mcp
56/100Currency A

Honua MCP Server ↗

Platform-free MCP server for geospatial services: expose discovery, query, and analysis over any public ArcGIS/Esri FeatureServer or OGC API endpoint to any MCP client, with no platform lock-in

What's in it

Data offered docs-verified
GeoServices (Esri) client · OGC API Features · OGC API Tiles (beta) · OGC API Maps (beta) · OGC API Processes · STAC · WMS · WMTS · WFS 2.0 · OData v4 · MapLibre data-to-map bridge · Provider-pluggable geocoding and routing
Formats docs-verified
GeoArrow batches (experimental columnar data plane) · MCP server
Access docs-verified
Open source, Apache-2.0 licence (per ENTRY). Public endpoints need no API key or account. Server-attach capabilities need a Honua Server. ENTRY lists HONUA_ADMIN_KEY, HONUA_API_KEY and HONUA_BEARER_TOKEN, which do not appear in the supplied DOCS.

Useful for

Use cases llm-inferred
Inspect and bounded-query a public ArcGIS FeatureServer or OGC endpoint, then map it in MapLibre for a site-constraints review · Build a styled 2D map of WMS or WFS layers as an EIA or planning baseline, using the same typed client for each protocol · Scan an existing ArcGIS web app for classic widgets and migrate it to MapLibre before the ArcGIS JS 6.0 removal · Give a coding agent typed access to live geospatial endpoints for scripted data checks
Audience llm-inferred
GIS analysts · web and GIS developers · geospatial data engineers · planners and ecologists working with agent-assisted queries

Limitations

Constraints llm-inferred
Release status is beta (0.2.2); 26 experimental subpaths may change before 1.0 · The README tracks the development branch; the npm artifact may not include every described capability · It is a client SDK and supplies no datasets itself; coverage depends entirely on the endpoint queried · Entry metadata lists region as Global, and nothing in the DOCS is UK-specific · Server-attach capabilities (8 of 36 claims) need a Honua Server · The columnar data plane is experimental, the Cesium scene surface is beta and Kepler.gl is experimental · Multi-source service roots need an explicit sourceId · Unsupported capabilities throw HonuaCapabilityNotSupportedError · The map path needs maplibre-gl installed as a peer dependency · MCP transport and tool names are not stated in the supplied DOCS
gis

Some details auto-extracted · unverified

Globalrestricted

Frequently asked questions

Which listed sources support Planning constraints GIS MCP?

Start with planning.data.gov.uk, MAGIC, Historic England NHLE open data. Overlay planning designations, protected sites and listed assets around a project boundary.

What should I check before using these sources for planning constraints gis mcp?

Layer coverage and update cycles differ; confirm constraints with the responsible authority.

How do I inspect planning.data.gov.uk through MCP?

Connect an MCP client to https://terramcp.earth/mcp and call get_source with slug planning-data-gov-uk. Review its provenance, access requirements and limitations before contacting the upstream service. Discovery does not make every listed source directly executable through the router.

Are these sources free and independently verified?

Access and licence terms belong to each upstream provider; some products require registration or payment. Open each listing for evidence, health status and enrichment provenance. A wrapper and its underlying API can refer to the same dataset and are not independent observations.