Zippopotam.us MCP. Get Coordinates from Any Global Zip Code

This server gives your AI agent access to global address intelligence via Zippopotam.us. You're not just running a simple lookup; you’re connecting to an instant, universal postal authority for anything involving physical addresses. It handles everything from validating one zip code to mapping out all the codes in an entire state.

Your agent executes two specific functions: lookup_postcode validates a location using a single zip code input; lookup_nearby_city generates a comprehensive list of codes when you only know the general area. You'll find it essential for any workflow touching logistics, data completeness, or geo-validation.

Validating Location by Postal Code with lookup_postcode

When your client needs to verify if an address exists and where it is on a map, you use the lookup_postcode tool. You pass it one specific postal code as input. The server immediately returns structured data containing the corresponding city name, the state abbreviation, and precise geographic coordinates (latitude and longitude) for that exact location.

This process verifies all components of the address simultaneously. If the provided zip code is valid, you'll get a complete picture: not just the city or state, but where on Earth it sits.

Mapping All Codes for a City/State with lookup_nearby_city

Sometimes, you don't have a specific postal code; you just know the general area—you've got a city and its state. For that, you use lookup_nearby_city. You input the target city and the state name. The server then runs through its database and returns every single valid postal code associated with that entire combination of city and state.

This is critical when you need to batch process data or fill in gaps where users only provide a general location, not an exact code. It gives you maximum coverage for any given municipality.

How the Tools Work Under the Hood

The system operates on clean inputs and structured outputs. When your agent calls the server via your preferred client, it specifies which tool it needs: if it’s validation, it uses lookup_postcode; if it’s mapping a region, it uses lookup_nearby_city. The output is always reliable JSON data. For example, using lookup_postcode, you send the zip code, and you get back the city name, state abbreviation, latitude, and longitude in one packet.

With lookup_nearby_city, you give it 'Dallas' and 'Texas,' and it sends back a list containing dozens of valid postal codes that belong to Dallas, Texas.

It’s built for rigor. You don't get fuzzy results or approximations. You get actionable geographic intelligence. This capability is perfect for databases needing completeness checks, billing systems requiring accurate location validation before processing, or any system dealing with physical goods where knowing the exact boundaries matters.