Access UK planning application data via PlanWire API for search, lookup, and location queries with MCP clients.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
The install command below started, but didn't respond the way we expected when we tried to talk to it.
npx -y planwire-mcpinitialize succeeded but no response to tools/list.
This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Planwire MCP.
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.
Use UK planning application data inside Claude, Cursor, and any MCP client.
PlanWire exposes fresh, normalised UK planning application data through a public API. This MCP server wraps that API as agent tools so an assistant can search applications, inspect a specific record, look near a location, and list supported councils without you writing API calls by hand.
Get a free sandbox API key at https://planwire.io/?utm_source=npm&utm_medium=mcp_readme&utm_campaign=mcp.
Model Context Protocol (MCP) is a standard way for AI tools to call external services. You run this package locally through npx; it talks to PlanWire using your own API key and returns structured planning data to the MCP client.
This server uses stdio transport. It does not store credentials or run a hosted proxy.
You need Node.js 18+ and a PlanWire API key.
Use the package name exactly as shown: planwire-mcp. If an MCP directory shows an install command for beshogun-planwire-mcp, that directory has stale generated metadata and the install will fail.
The server expects PLANWIRE_API_KEY in the environment. Optional: set PLANWIRE_API_BASE to override the default https://api.planwire.io.
Add this to claude_desktop_config.json:
Restart Claude Desktop after saving the config.
Add this to your project .mcp.json:
Add the same server command in Cursor's MCP settings:
| Tool | What it does |
|---|---|
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. |
Free sandbox keys are suitable for testing and are capped on daily calls and result size. Paid plans increase limits for production use.
Pricing: https://planwire.io/?utm_source=npm&utm_medium=mcp_readme&utm_campaign=mcp#pricing
If the tool says PLANWIRE_API_KEY is not set, add your key to the MCP client config and restart the client.
If PlanWire returns 401, check that the key is correct and active.
If PlanWire returns 429, the key has reached its rate limit. Use fewer calls or upgrade at https://planwire.io/?utm_source=npm&utm_medium=mcp_readme&utm_campaign=mcp#pricing.
MIT licensed. Built by PlanWire: https://planwire.io/?utm_source=npm&utm_medium=mcp_readme&utm_campaign=mcp
Factual signals from GitHub, npm, and our automated checks — not a rating.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/beshogun-planwire-mcp)<a href="https://allmcps.com/mcp/beshogun-planwire-mcp"><img src="https://allmcps.com/api/badge/beshogun-planwire-mcp?style=directory" alt="Planwire MCP on AllMCPs" /></a>