Planwire MCP Server

UK planning application data for AI agents: search, geo-query and fetch applications.

Remote serverstreamable-http

What is the Planwire MCP server?

Connect Planwire to Claude, Cursor or any other MCP client and it stops being a tab you switch to. UK planning application data for AI agents: search, geo-query and fetch applications. The planwire mcp server is what makes that connection.

What the server does

Use UK planning application data inside Claude, Cursor, and any MCP client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • search_planning_applications — Search by keyword, council, postcode, status, type, or date range
  • nearby_planning_applications — Find applications near a latitude/longitude point
  • get_planning_application — Fetch one application by PlanWire application id
  • list_councils — List covered councils and their IDs

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: PLANWIRE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Planwire's toolset — search_planning_applications, nearby_planning_applications, get_planning_application and 1 more — is a fair guide to whether it matches your workflow. It is maintained by beshogun; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Planwire's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
search_planning_applicationsSearch by keyword, council, postcode, status, type, or date range.
nearby_planning_applicationsFind applications near a latitude/longitude point.
get_planning_applicationFetch one application by PlanWire application id.
list_councilsList covered councils and their IDs.

How to install the Planwire MCP server

{
  "mcpServers": {
    "planwire": {
      "command": "npx",
      "args": ["-y", "planwire-mcp"],
      "env": {
        "PLANWIRE_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
PLANWIRE_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Planwire to search planning applications.
  • Use Planwire to nearby planning applications.
  • Use Planwire to get planning application.

Frequently asked questions

It connects Planwire to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (search_planning_applications, nearby_planning_applications, get_planning_application, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Planwire directly.