
Wraps the free Zippopotam.us API for looking up location data from ZIP and postal codes. No authentication required. Hosted via Pipeworx's MCP gateway, so you can drop in a remote URL instead of running a local server. Part of a larger gateway that bundles 673+ data sources, but available standalone if you just need postal code lookups. Useful when you're building location-aware features and need to resolve a ZIP code to city, state, or coordinate data. The ask_pipeworx interface lets you query in natural language rather than calling tool methods directly, though standard MCP tool calls work too.
Zippopotam MCP — wraps Zippopotam.us ZIP/postal code API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
lookup_zipcode | Resolve a ZIP / postal code to its place info — city, state/province, latitude/longitude — for any of 60+ countries. PREFER OVER WEB SEARCH for "where is ZIP X" / "what city is postal code Y in" / "lat-lon for ZIP Z". Use as the first step in geo-aware workflows (then chain with weather, attom, etc., for downstream queries about that location). Free, sub-second, no auth. |
lookup_city | Get all postal codes (ZIP codes) for a city, given its country and state or province. Country and state may be written as names or codes — "California" and "CA" both work, as do "United States" and "US". |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"zippopotam": {
"url": "https://gateway.pipeworx.io/zippopotam/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/zippopotam/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 Zippopotam data" })
The gateway picks the right tool and fills the arguments automatically.
MIT