
Planwire Mcp
io.github.beshogunPublished by GitHub account beshogunv0.1.4Updated Oct 24, 2026
UK planning application data for AI agents: search, geo-query and fetch applications.
The publisher's own server: Milewise
Overview
A local MCP server that gives an AI assistant read access to UK planning application data through the PlanWire API.
- What you can do
- Search planning applications by keyword, council, postcode, status, type or date range, and find applications near a latitude/longitude point. Fetch a single application by its PlanWire ID. List the councils covered and their IDs.
- When to use it
- Useful when you want an assistant to look up UK planning applications, check what has been submitted or refused in an area, or explore records near a location without writing API calls yourself.
- Requirements
- Runs locally via npx, so Node.js 18+ is needed. Requires a PlanWire API key supplied in the PLANWIRE_API_KEY environment variable; a free sandbox key is available. Network access to the PlanWire API is required, and PLANWIRE_API_BASE can override the default endpoint.
Installation
In SourceWeft
- Open Planwire Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
PlanWire MCP Server
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.
What MCP Is
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.
Install
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.
Claude Desktop
Add this to claude_desktop_config.json:
Restart Claude Desktop after saving the config.
Claude Code
Add this to your project .mcp.json:
Cursor
Add the same server command in Cursor's MCP settings:
Tools
Example Prompts
- "Search PlanWire for recent planning applications in Camden."
- "Find refused householder extensions in OX1 from the last year."
- "What planning applications are within 1km of 51.5074, -0.1278?"
- "List the councils PlanWire covers."
- "Find planning applications mentioning HMOs in Manchester."
Limits And Pricing
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
Troubleshooting
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.
Development
MIT licensed. Built by PlanWire: https://planwire.io/?utm_source=npm&utm_medium=mcp_readme&utm_campaign=mcp
Source: README.md at commit f399b16
Tools
0Version history
1- v0.1.4LatestSep 16, 2026
Score
40% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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
- License10 pts
Declare a license in the repository or the registry entry.
