OpenCage MCP. Convert Addresses to Coordinates & Back.

When your agent needs to figure out a location, OpenCage handles both ends of the street: converting a raw address string into precise coordinates, or taking a GPS pin and turning it back into a readable street address. You'll use these tools by calling them directly from your AI client.

Forward Geocoding (Address to Coordinates)

When you start with an address—say, '123 Main St'—you run the core lookup using geocode_basic for a general search within OpenCage boundaries. If that initial result is ambiguous or if you need confirmation on multiple delivery points, use geocode_all_duplicate_results; it retrieves structural matches confirming those alternative options. You don't wanna guess; you gotta be precise.

To make sure your location data is trustworthy enough for production, you can run the search with strict validation using geocode_high_confidence. This tool requires you to set explicit score limits (1–10), guaranteeing that the coordinates returned are highly validated. If you're working internationally, you don't want generic results; use geocode_language_bias to get results localized in a specific language code, like pt-BR, which handles tricky international address formats.

You can also narrow down your search dramatically using filters. To keep the location confined, employ geocode_bounding_box, which restricts searches to a precise geographic rectangle (a polygon). If you only care about one country, use geocode_country_filter and pass the specific two-letter code; this guarantees the address match belongs only to that nation.

When privacy is your biggest concern, forget logging anything down. You run location lookups without OpenCage ever recording the query by calling geocode_no_record_privacy.

Reverse Geocoding (Coordinates to Address)

If you've got a raw latitude/longitude pair—a GPS pin—and need to know what street it belongs to, start with reverse_basic. This lists structured rules that export active GPS data into an easily readable address format. For quick lookups where you just need the location array and don't want extra details slowing things down, use reverse_fast_no_annotations; this identifies accurate location arrays spanning native boundaries fast.

If you need more than just the street name from a pin, you can pull in time data. The reverse_fetch_time_annotations tool extracts UTC logic from GPS pins. That gives you historical validation limits like sunrise and sunset times for that exact spot.

Overall, your agent handles these tasks by converting addresses to coordinates or vice versa, while letting you restrict the results using filters for country code, bounding boxes, confidence scores, or language bias.