# Country Data Resolver MCP

> Country Data Resolver resolves any two-letter country code (like 'BR' or 'JP') into its full name, alpha-3 code, and numeric ID. It handles this across four languages: English, Portuguese, Spanish, and French. This is essential for CRMs and Martech platforms that deal with international contact lists and need accurate data normalization.

## Overview
- **Category:** utilities
- **Price:** Free
- **Tags:** country, iso, i18n, crm, localization

## Description

When your agent needs to process a global list of contacts, it can't just guess what 'MK' means; the code could stand for anything. This MCP solves that problem immediately. It takes any ISO 3166-1 alpha-2 code and spits out the full country name, plus its standardized three-letter (alpha-3) and numeric codes. You can even specify which language you want the output in—English, Portuguese, Spanish, or French. This eliminates manual lookups from massive reference sheets. With Vinkius managing this MCP in your catalog, you connect once and get reliable international data resolution for all your projects.

## Tools

### resolve_country
Pass an alpha-2 country code and an optional language to get the full name, alpha-3 code, and numeric identifier.

## Prompt Examples

**Prompt:** 
```
What is the full name for country code BR in Portuguese?
```

**Response:** 
```
Country: Brasil (alpha-3: BRA, numeric: 076)
```

**Prompt:** 
```
Resolve the country code MK to its full name.
```

**Response:** 
```
Country: North Macedonia (alpha-3: MKD, numeric: 807)
```

**Prompt:** 
```
Get all ISO codes for Japan.
```

**Response:** 
```
Country: Japan (alpha-2: JP, alpha-3: JPN, numeric: 392)
```

## Capabilities

### Standardize Country Identifiers
Take a simple two-letter code (like 'DE') and convert it into its full name, alpha-3 code, and numeric ID.

### Localize Output Names
Specify the output language for country names—English, Portuguese, Spanish, or French—ensuring local relevance in reports.

### Enrich Contact Data
Quickly map raw international codes found in a spreadsheet to validated, structured data fields.

### Validate Global Inputs
Prevent downstream errors by checking if an obscure or incomplete code matches any known country record.

## Use Cases

### Cleaning up a Global Lead List
A marketing ops specialist gets a spreadsheet of leads from various regions. Instead of manually checking every two-letter code to confirm the country, they ask their agent to run `resolve_country` on the whole list. The agent returns clean records with full names and numeric IDs ready for import into Salesforce.

### Building a Multilingual App Feature
A developer needs an app that displays country information in Spanish, regardless of where the user is located. They use their agent to call `resolve_country` with the code and specify 'es' for the language. The resulting structured data populates the correct field in the UI.

### Validating Database Migrations
A data scientist is migrating an old database that only used raw two-letter codes. Before running a script, they use their agent to test every code through `resolve_country` to ensure the full names and alpha-3 tags are consistent and available.

### Handling Obscure Codes
A user finds an old record with a rarely seen two-letter country code. They prompt their agent, asking for resolution. The MCP quickly identifies the full name (e.g., North Macedonia) and provides all three necessary codes, preventing data loss.

## Benefits

- Stop guessing country names. The `resolve_country` tool guarantees that when your agent sees 'BR', it knows exactly what Brasil is, along with its official alpha-3 and numeric codes.
- Handle multilingual data effortlessly. Need the name in Portuguese for a campaign targeting Brazil? Just ask, and the MCP provides the correct translation instantly.
- Keep your CRM clean. By using this MCP, you eliminate manual lookups from massive reference sheets, ensuring every contact record is standardized globally.
- Save time on complex pipelines. Instead of running three separate API calls (one for name, one for alpha-3, one for numeric), the tool bundles all data into a single output.
- Future-proof your system. When dealing with international expansion, this MCP gives you validated codes and names for over 249 countries.

## How It Works

The bottom line is you stop manually cross-referencing country lists; your agent gets clean, standardized location data immediately.

1. You give your agent the two-letter country code and optionally tell it which language to use for the name.
2. The MCP runs the code against its database, pulling all associated identifiers (full name, alpha-3, numeric ID) and translating the name if requested.
3. Your agent receives a structured output containing the full country name and all required codes in one go.

## Frequently Asked Questions

**How does the Country Data Resolver MCP resolve country codes?**
It resolves codes by matching them against a comprehensive ISO 3166-1 database. You pass the two-letter code and let the MCP pull all associated identifiers (name, alpha-3, numeric) for you.

**Can I use `resolve_country` to get multiple languages?**
Yes. The tool accepts an optional language parameter, allowing you to request the full country name in English, Portuguese, Spanish, or French for consistency across campaigns.

**Is this MCP only for CRM data?**
No. While perfect for CRMs and Martech, it's useful anywhere structured international data is involved—like logistics planning or academic research databases.

**What happens if the country code I provide doesn't exist? (using resolve_country)**
The MCP is designed to handle invalid inputs. It won't guess; it will return an error state, letting your agent know immediately that the code needs correcting before proceeding.

**Are there limits on how many times I can use the `resolve_country` tool in one workflow?**
Vinkius manages the underlying API rate limits for this MCP. If you hit a usage threshold, your agent will receive a standard rate-limit error. You'll need to implement exponential backoff logic in your code to retry the call later.

**What kind of authentication do I need to use `resolve_country` with my AI client?**
You only need to connect your preferred agent through Vinkius. The MCP handles all necessary credential management internally, so you don't manage any API keys or special permissions for this specific utility.

**Does `resolve_country` support obscure country codes that might not be in the standard ISO 3166-1 list?**
The MCP uses a full database of 249 countries, adhering strictly to the established ISO 3166-1 standards. If an alpha-2 code isn't recognized globally by those standards, the tool won't resolve it.

**When using `resolve_country`, what is the best way to ensure I get all three types of codes (alpha-3, numeric)?**
Just pass the alpha-2 code and specify your desired language in the prompt. The tool returns all available identifiers—the full name, alpha-3, and numeric codes—in a single response object.

**How many countries are supported?**
All 249 countries and territories in the ISO 3166-1 standard, including overseas territories and special regions.

**What languages are available for country names?**
English (en), Portuguese (pt), Spanish (es), and French (fr). The engine defaults to English if the requested language is not available.

**Does it validate country codes?**
Yes. If you pass an invalid code like 'XX', the engine returns a clear error instead of guessing. This prevents data corruption in CRM systems.