England Planning Constraints Checker (official open data)

io.github.grant1493-svgPublished by GitHub account grant1493-svgv1.0.0Updated Oct 24, 2026

Planning constraints for English properties from official planning.data.gov.uk data, via Apify.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

An Apify-hosted MCP server that lets an assistant look up planning constraints for English properties using official planning.data.gov.uk data.

What you can do
Look up planning constraints for a property in England, drawing on official planning.data.gov.uk data through an Apify actor. Results are returned through the Apify MCP endpoint rather than computed locally.
When to use it
Useful when you need quick checks of planning constraints on English properties, for example during early property research or due diligence, without querying the planning.data.gov.uk sources yourself.
Requirements
A remote MCP connection to the Apify endpoint (mcp.apify.com) with OAuth authentication; an Apify API token sent as a Bearer token in the Authorization header, from a free Apify account. Usage is billed per event.
Before you install
Requires an Apify API token as a credential in the Authorization header, and usage is charged per event, so costs can accrue. Queries are sent to Apify's hosted service. Results come from official open data but should be verified before relying on them for decisions.

Installation

In SourceWeft

  1. Open England Planning Constraints Checker (official open data) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.grant1493-svg%2Fengland-planning-constraints/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "england-planning-constraints-checker-off": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=shelly_fen/england-planning-constraints-checker"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 14, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.