planwire-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLANWIRE_API_KEY | Yes | Your PlanWire API key (free sandbox, no card required). Obtain from https://planwire.io | |
| PLANWIRE_API_BASE | No | Base URL for the PlanWire API. Override if needed. | https://api.planwire.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_planning_applicationsA | Search UK planning applications by keyword, council, postcode, status, type, or date range. Returns matching applications with address, description, reference, status, and dates. Use for questions like 'recent planning applications in Camden' or 'refused extensions in OX1'. |
| nearby_planning_applicationsA | Find planning applications within a radius of a point (latitude/longitude). Use for 'what's been applied for near this location'. |
| get_planning_applicationA | Fetch a single planning application by its PlanWire id. |
| list_councilsA | List the UK councils (local planning authorities) PlanWire covers, with their IDs for use in searches. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: fetching by ID, listing councils, spatial search, and keyword search. No overlap in functionality.
Most names follow a verb_noun pattern (get, list, search), but 'nearby_planning_applications' omits a verb, creating a slight inconsistency. Otherwise snake_case is used consistently.
Four tools cover the core needs of the domain (search, detail retrieval, council reference) without excess or deficiency.
The set covers essential read operations: keyword search, spatial search, and detail retrieval. A minor gap is the lack of a tool to get an application by reference number, but most workflows are supported.