# beshogun/planwire-mcp [Health: Active]

**Category:** 🏠 Real Estate  
**Repository:** https://github.com/beshogun/planwire-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 306  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/beshogun-planwire-mcp

## Description
UK planning application data for AI agents: search planning applications by council, postcode, keyword, status, type, or date range; find applications near a lat/lng point; fetch a specific application; and list supported councils. Requires a PlanWire API key. npx -y planwire-mcp

## Tools
Capabilities this server exposes over MCP:

- **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.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

**Requires environment variables:** `PLANWIRE_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What beshogun/planwire-mcp does

The beshogun/planwire-mcp MCP server makes PlanWire’s UK planning application data available to AI clients through MCP tools. PlanWire provides fresh, normalised application records, while this package handles the connection between the MCP client and the PlanWire API.

It supports several common research patterns: searching applications with multiple filters, finding records around a geographic point, retrieving a known application, and checking which councils are covered. This suits workflows such as reviewing recent applications in a postcode, locating proposals near coordinates, or investigating applications that mention a particular term.

## How it works

The package runs locally as a Node.js process and uses stdio transport. An MCP client starts the process with `npx -y planwire-mcp`, and the process sends requests to PlanWire using the API key provided in its environment. Results are returned to the client as structured planning data.

The server does not store credentials and does not provide a hosted proxy. Its API access is performed with the user’s own PlanWire key. The default API endpoint is `https://api.planwire.io`, with an optional environment setting available when a different base URL is needed.

## Setup and configuration

The beshogun/planwire-mcp MCP server requires Node.js 18 or newer and a PlanWire API key. Obtain a key from PlanWire, then configure the MCP client to launch the package with the required environment variable:

```json
{
  "mcpServers": {
    "planwire": {
      "command": "npx",
      "args": ["-y", "planwire-mcp"],
      "env": {
        "PLANWIRE_API_KEY": "your_planwire_key_here"
      }
    }
  }
}
```

The same command pattern can be added to Claude Desktop, Claude Code, or Cursor. Use the package name `planwire-mcp`; `beshogun-planwire-mcp` is identified in the documentation as stale metadata and is not the valid install name. Set `PLANWIRE_API_BASE` only if the default PlanWire endpoint should be overridden.

## Tools and capabilities

- `search_planning_applications` searches by keyword, council, postcode, status, type, or date range.
- `nearby_planning_applications` finds applications near a supplied latitude and longitude.
- `get_planning_application` retrieves one record using its PlanWire application ID.
- `list_councils` returns supported councils and their PlanWire IDs.

These tools can be combined in an agent workflow: list councils first when a council ID is needed, search using the available criteria, then retrieve a specific result for closer inspection.

## Limitations and notes

The beshogun/planwire-mcp MCP server only exposes data available through PlanWire and its supported councils. Free sandbox keys are intended for testing and have daily-call and result-size caps. Paid plans provide higher limits for production use.

An unset `PLANWIRE_API_KEY` prevents the server from authenticating. A `401` response usually indicates an invalid or inactive key, while a `429` response indicates that the key has reached its rate limit. Reduce request volume or use a plan with higher limits when appropriate.

The package uses local stdio transport, so the MCP client must be able to launch a local Node.js command. It is not a hosted service or proxy.

_Full upstream README: https://allmcps.com/mcp/beshogun-planwire-mcp/readme_