MCP server
UK planning application data inside Claude, Cursor, and agent workflows.
Install the PlanWire MCP server to let an AI client search planning applications, find nearby applications, fetch individual records, and list covered councils using your own PlanWire API key.
"Search PlanWire for recent planning applications in Camden, then show any refused householder extensions near NW1."
{
"tool": "search_planning_applications",
"arguments": {
"council": "camden",
"status": "Refused",
"type": "Householder",
"postcode": "NW1",
"limit": 10
}
}
What MCP is
Model Context Protocol lets AI clients call external tools. PlanWire MCP exposes the public PlanWire API as tools an agent can use during a conversation.
What it can access
The server calls PlanWire with the API key you provide. It does not store credentials and does not access council portals itself.
Who it is for
PropTech teams, researchers, analysts, and operators who want planning data inside Claude, Cursor, internal agents, or reporting workflows.
Package and source
Open-source MCP package for PlanWire
The package runs locally with stdio, uses your own PlanWire API key, and is published as `planwire-mcp` for any MCP client that can launch an npm command.
GitHub source
Read the code, configuration, and tool definitions before installing.
npm package
Install with `npx -y planwire-mcp` and provide `PLANWIRE_API_KEY`.
MCP directory
View the PlanWire server profile in MCP Market.
mcpbeat listing
Install examples for Claude, Codex, Cursor, VS Code, and other local MCP clients.
PluginBench listing
Registry metadata, package details, and generated client configuration.
SyncDev listing
Reviewed tool summary for teams comparing MCP servers.
Install
Claude Desktop / Claude Code config
Add this to `claude_desktop_config.json`, or to `.mcp.json` in a project. Replace `your_key_here` with a key from PlanWire.
{
"mcpServers": {
"planwire": {
"command": "npx",
"args": ["-y", "planwire-mcp"],
"env": {
"PLANWIRE_API_KEY": "your_key_here"
}
}
}
}
Cursor
Use the same command, `npx -y planwire-mcp`, with `PLANWIRE_API_KEY` in the environment.
Direct stdio
Any MCP client that supports stdio can launch `planwire-mcp` and pass the same environment variable.
Tools
Four agent tools over the PlanWire API
search_planning_applications
Search by keyword, council, postcode, status, type, date range, page, and limit.
nearby_planning_applications
Find applications within a radius of a latitude/longitude point.
get_planning_application
Fetch one planning application by PlanWire application id.
list_councils
List covered local planning authorities and their council IDs.
Examples
Prompts to try
These work once your MCP client has restarted and loaded the PlanWire server.
Limits
Uses your normal PlanWire API limits
The MCP server is a thin wrapper over the public API. Free keys are intended for light testing; paid plans provide higher request limits, larger result pages, and production use.