# OpenCage MCP for AI Agents AI Agent Connect > OpenCage MCP for AI Agents. It converts addresses into coordinates and turns GPS pins into readable street addresses. Use it to get precise location data with filters for country, language, and accuracy. It's built for logistics, data enrichment, and privacy-focused apps that need reliable geocoding. ## Overview - **Category:** developer-tools - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_WKDzyl3VZM3raWteXPmOlZb4ewVy4fXLQllarGvU/ai-agent-connect - **Tags:** geocoding, reverse-geocoding, location-intelligence, spatial-analysis, timezone-data, data-validation ## Description Imagine you're building an app that needs to know exactly where a user is located, or you're trying to organize a massive dataset of global addresses into a map. Usually, this means juggling multiple APIs, worrying about inconsistent results, and guessing which "Springfield" the data actually refers to. This Connector changes that by giving your AI agent direct access to OpenCage's geocoding engine. You can ask your agent to find coordinates for a specific street, turn a GPS pin into a readable address, or even filter results so you only see locations in a specific country. It handles the heavy lifting of data validation, like checking for duplicate entries or setting confidence scores to ensure you aren't getting junk data. Because it's part of the Vinkius catalog, you don't have to set up complex integrations for every new project. You just connect it once and let your agent handle the spatial analysis. Whether you're trying to verify delivery points for a trucking fleet or enriching a database with timezone info, it provides the precision you need without the manual headache. ## Tools ### geocode_bounding_box Inspects internal arrays to limit results to a specific geographic rectangle. It helps narrow down search areas. ### geocode_high_confidence Runs automated checks to ensure results meet your minimum confidence score. It keeps your data accurate. ### geocode_country_filter Extracts properties to ensure results only show for specific country nodes. This prevents matching the wrong city. ### geocode_language_bias Retrieves location data in specific locales like French or Brazilian Portuguese. It helps with localized data. ### geocode_all_duplicate_results Finds exact structural matches to verify different delivery alternatives. This is great for data validation. ### geocode_no_record_privacy Generates secure mappings without logging the query data. Use this for sensitive user information. ### reverse_basic Lists structured rules to export active GPS pins into readable addresses. It turns numbers into names. ### reverse_fetch_time_annotations Extracts UTC logic from location data without keeping validation limits. This is useful for keeping your data clean. ### reverse_fast_no_annotations Identifies location arrays faster by removing unnecessary metadata. It's the best choice for high-speed lookups. ### geocode_basic Identifies bounded routing spaces within the OpenCage engine. Use this for standard address to coordinate lookups. ## Prompt Examples **Prompt:** ``` What are the coordinates for the Eiffel Tower? ``` **Response:** ``` I've located the Eiffel Tower for you. Here are the details: | Data Point | Value | | :--- | :--- | | **Latitude** | 48.8584 | | **Longitude** | 2.2945 | | **Timezone** | Europe/Paris (CET, UTC+1) | | **Confidence** | 10/10 | The result is formatted for standard use. Would you like me to find more landmarks nearby? ``` **Prompt:** ``` What's at 48.8566, 2.3522? ``` **Response:** ``` That's a famous spot in Paris, France. **Address:** Rue de Rivoli, 75001 Paris, France. **Timezone:** Europe/Paris (CET, UTC+1). **Country Code:** FR. Would you like me to strip the annotations for a faster response next time? ``` **Prompt:** ``` Find 'Springfield' in the US with a confidence of at least 8. ``` **Response:** ``` I found 5 matches for 'Springfield' in the United States with a confidence score of 8 or higher: * **Springfield, IL** (Confidence: 9) - 39.7817, -89.6501 * **Springfield, MO** (Confidence: 8) - 37.5401, -92.3731 * **Springfield, MA** (Confidence: 8) - 42.1670, -72.5940 * **Springfield, OH** (Confidence: 7) - 40.4173, -82.4611 * **Springfield, OR** (Confidence: 7) - 46.7596, -123.0941 Do you want me to get more details on any of these? ``` ## Capabilities ### Convert addresses to coordinates Turn any physical address or place name into exact latitude and longitude points. ### Turn GPS pins into addresses Convert raw coordinates into structured street addresses with timezone and sun data. ### Filter by specific countries Restrict search results to a specific country to avoid getting matches from the wrong region. ### Localize results by language Request location data in specific languages like French, Portuguese, or Spanish. ### Set minimum confidence levels Filter out low-quality matches by requiring a specific confidence score for better accuracy. ### Constrain searches to a box Limit your results to a specific geographic rectangle for targeted regional searches. ### Run queries in private mode Perform geocoding tasks without the service logging your sensitive address data. ## Use Cases ### Validating a fleet's delivery points A fleet manager asks the agent to check if 500 new delivery addresses are valid and geocode them for a specific zip code. ### Enriching a global landmark dataset A researcher asks the agent to find the coordinates and timezones for a list of 1,000 global landmarks in a CSV. ### Finding nearby spots in a city A developer wants to see what's near a set of coordinates while staying strictly within a specific city boundary. ### Geocoding clinic locations privately A healthcare app needs to geocode clinic locations without storing the query history in external logs to stay compliant. ## Benefits - Stop guessing locations by using geocode_country_filter to isolate results to one nation. - Improve delivery success rates by validating addresses with geocode_high_confidence scores. - Protect user privacy by using geocode_no_record_privacy to run queries without logging. - Handle global data easily with geocode_language_bias to get localized results for international users. - Speed up your workflows using reverse_fast_no_annotations for quick GPS-to-address conversions. ## How It Works The bottom line is that you get accurate, filterable location data through a simple chat interface. 1. Subscribe to this Connector and grab your OpenCage API key. 2. Plug your key into your AI client settings. 3. Ask your agent to geocode addresses or find locations in plain English. ## Frequently Asked Questions **Can OpenCage MCP help me validate my shipping addresses?** Yes, it can. You can ask your agent to check if a list of addresses is valid and get back precise coordinates and confidence scores to ensure they are deliverable. **How does OpenCage MCP handle privacy for sensitive data?** It includes a specific privacy mode. This allows your agent to perform geocoding tasks without the service logging your sensitive address data in third-party logs. **Can I get coordinates for addresses in different languages?** Yes, the Connector supports language bias. You can request results in specific locales like French, Portuguese, or Spanish to match your dataset's needs. **How does the confidence score work in OpenCage MCP?** The tool provides a score for every match. You can tell your agent to only show results that meet a certain threshold, like a 7 or 8, to filter out low-quality data. **Can I limit my search to a specific city or area?** Absolutely. You can use bounding box constraints to limit results to a specific geographic rectangle or use country filters to stay within one nation. **Does OpenCage MCP provide timezone information?** Yes, it returns timezone data along with the address and coordinates, making it easy to enrich your location data for global apps. **How accurate is the geocoding — can I use it for delivery routing?** OpenCage returns a confidence score from 1 to 10 for each result. Use the high-confidence filter (min_confidence=8 or higher) to get delivery-grade accuracy. Combined with country filtering, you can eliminate ambiguous matches and get coordinates reliable enough for last-mile dispatch. **What does privacy mode actually do?** When you enable no_record=1, OpenCage processes your query but doesn't log it in their cache or analytics. The result is identical, but the query leaves no trace on their servers. Ideal for geocoding patient addresses, legal documents, or any PII-sensitive data. **Can I geocode in multiple languages — like getting results in Portuguese for a Brazilian address?** Yes. Use the language bias tool with any IETF language code (pt-BR, es-MX, fr-FR, etc.) and OpenCage returns the address components translated to that locale. Perfect for building multilingual apps or standardizing address formats across regions.