LocationIQ MCP. Convert addresses, calculate routes, and map coordinates.

You're dealing with location data, right? You need to know where something is, or you gotta figure out how to get there. This LocationIQ server handles all that heavy lifting for geocoding, routing, and mapping lookups. It lets your AI client turn messy addresses into clean GPS coordinates, calculate complex travel times across multiple stops, and even translate raw coordinates back into local language addresses.

When you need to pinpoint an exact location from a text address, use search_geocode. You feed it any standard street address string, and it spits out precise latitude/longitude pairs that conform to OpenStreetMap standards. If the user is typing out an address and you want real-time help guiding them to the right spot, trigger search_autocomplete; it provides instant suggestions for partial location queries, helping narrow down search terms fast.

You can make those searches even more precise by limiting the results using two specific filters: first, if you only care about locations within a defined region, use search_bounding_box. If the address has to be in a certain country, force the hand with search_country_filter to limit results solely to that nation's ISO code.

On the flip side, if you only have raw coordinates—say, a floating point from an old sensor reading—but need to know what street it's actually on, run snap_nearest_roads. This tool adjusts those messy GPS signals until they sit perfectly on the nearest known road or street segment. To go backward and find out what human-readable address corresponds to raw latitude/longitude points, use reverse_geocode.

It converts those coordinates into standard, usable postal addresses. If you're dealing with international clients and need that address translated for them, trigger reverse_language_bias; it takes the coordinates and returns the full address written in a specific native language tag.

For figuring out travel paths, LocationIQ gives you two key tools. To get the single best path—whether driving, walking, or biking—between just a start point and an end point, use calculate_directions. It figures out the optimal route based on your chosen mode of transport. If you're planning logistics for multiple stops and need to know how long it takes to travel between every pair of locations, run calculate_distance_matrix.

This generates a detailed table showing the estimated distance and duration among all your starting points and destinations. Finally, if you just want to check how many API calls you've left for the day before running any big searches, use check_account_balance.