OpenCage Geocoder MCP. Convert any location to lat/lon or vice versa.

When you're dealing with location data, you gotta convert between addresses and coordinates constantly. The OpenCage Geocoder handles that whole round trip for your agent. This server gives your AI client the high-precision tools it needs to map anything globally.

How It Works

Your agent uses two primary functions: forward_geocode and reverse_geocode. You don't need to worry about the underlying API calls; you just tell your client what location data you have, and it handles the rest.

Using forward_geocode (Address to Coordinates)

When you pass in a physical address, place name, or landmark string, this tool spits out precise latitude and longitude numbers. It's reliable for everything: just a street corner, an entire city block, or even a specific ZIP code area. You can feed it anything from 'Times Square, New York' to 'The Eiffel Tower' and get coordinates back instantly.

What’s really useful is that you don't have to pick one format—it handles different international address standards globally. If you need extra detail, the tool can also grab specific road info; for instance, it tells you which nearest major road matches the location you provided.

Using reverse_geocode (Coordinates to Address)

If your agent only has coordinates—say, lat 34.0522 and lon -118.2437—this tool flips it around. It takes those raw numbers and turns them into a full, structured, readable street address. This isn't just random text; the output is formatted exactly like an actual mailing address, complete with necessary location metadata you need for databases or reports.

Global Scope and Flexibility

The coverage here is huge. It doesn't pull data from one place; it aggregates multiple open sources—think OpenStreetMap and other reliable global datasets—meaning it covers nearly every geographic region on the planet. You can specify exactly what language you want the results in, or what format your application needs, ensuring the output integrates smoothly into whatever system you’re running.

For instance, if you're processing international data, you might run forward_geocode with an address written in French, and the server gives you coordinates. Then, later on, when validating that point, you use reverse_geocode to ensure the resulting street address is also formatted correctly for a different language. It’s seamless because the underlying mechanism handles the linguistic complexity.

Don't try building this yourself with multiple APIs; it'll be a nightmare of keys and formatting rules. This server consolidates all that complex geocoding logic into one reliable, straightforward toolset. You just call forward_geocode or reverse_geocode, and you get clean, structured data back every time.