
Wraps the free postcodes.io API to give Claude geographic tools for UK postcodes without requiring authentication. You get four operations: lookup a postcode for coordinates and administrative boundaries like region, district, ward, and constituency; find nearby postcodes sorted by distance; validate postcode format; or pull a random valid postcode. Useful when you need to resolve UK addresses to lat/long, check if user input is a real postcode, or build location aware features for UK users. Runs through Pipeworx's gateway, which can bundle this with 673+ other data sources if you need broader API access beyond postcodes.
Postcodes MCP — wraps postcodes.io UK postcode API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
lookup_postcode | Get geographic details for a UK postcode (e.g., 'SW1A 1AA'). Returns coordinates, region, district, ward, and constituency. |
nearest_postcodes | Find nearby UK postcodes sorted by distance from a given postcode (e.g., 'SW1A 1AA'). Returns list with coordinates. |
validate_postcode | Validate a UK postcode format (e.g., 'SW1A 1AA'). Returns whether it's valid and format details. |
random_postcode | Get a random valid UK postcode with full geographic details. Returns coordinates, region, district, ward, and constituency. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"postcodes": {
"url": "https://gateway.pipeworx.io/postcodes/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/postcodes/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Postcodes data" })
The gateway picks the right tool and fills the arguments automatically.
MIT