Country Data Resolver MCP for AI. Map Any Country Code To Its Full Details.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
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.
What your AI can do
Resolve country
Pass an alpha-2 country code and an optional language to get the full name, alpha-3 code, and numeric identifier.
Take a simple two-letter code (like 'DE') and convert it into its full name, alpha-3 code, and numeric ID.
Specify the output language for country names—English, Portuguese, Spanish, or French—ensuring local relevance in reports.
Quickly map raw international codes found in a spreadsheet to validated, structured data fields.
Prevent downstream errors by checking if an obscure or incomplete code matches any known country record.
Ask an AI about this
Waiting for input…
Country Data Resolver: 1 Tool Available
This single tool lets your agent take a raw two-letter country code and output all associated full names, three-letter codes, and numeric IDs across four different languages.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Country Data Resolver on VinkiusResolve Country
Pass an alpha-2 country code and an optional language to get the full name, alpha-3 code, and numeric identifier.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Country Data Resolver, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by i18n-iso-countries. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 1 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Cleaning Up International Data is Always a Headache
Right now, if your team gets a list of contacts from global sources, you're faced with copy-pasting codes into spreadsheets. You have to check: Is 'MK' North Macedonia? What’s its alpha-3 code? And how do I get the name in French for this specific campaign? It takes hours just to normalize one dataset.
With this MCP, your agent handles all that grunt work. You give it the messy list and ask for resolution. The output isn't a bunch of raw data points; it’s clean, structured records with every code validated against its full name in multiple languages. It just works.
The `resolve_country` Tool Delivers Complete Location Data
You stop worrying about the three different codes (alpha-2, alpha-3, numeric) existing in isolation. You don't have to run multiple searches or rely on separate lookup tables for each data point.
What’s different now is reliability. Your agent gets a complete package of verified location details every time, letting you build robust pipelines without needing specialized geo-coding services.
What your AI can actually do with this
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.
019e387e-e9b5-70d3-a902-dc30e00caae5 Here's how it actually works
The bottom line is you stop manually cross-referencing country lists; your agent gets clean, standardized location data immediately.
You give your agent the two-letter country code and optionally tell it which language to use for the name.
The MCP runs the code against its database, pulling all associated identifiers (full name, alpha-3, numeric ID) and translating the name if requested.
Your agent receives a structured output containing the full country name and all required codes in one go.
Who is this actually for?
This MCP is for the Operations Engineer who deals with international datasets and hates cleaning messy contact records. It's also perfect for Data Scientists needing reliable inputs for global models, or anyone whose job involves CRM data from multiple continents.
They run reports on contacts from dozens of countries and need to ensure that a single two-letter code translates correctly into the right name for marketing segments.
They are building models based on global location data. This MCP provides validated, consistent inputs—like alpha-3 codes—so their features don't break when a new country is added to the dataset.
They manage international email lists and must know if a code like 'MK' translates into North Macedonia across different language campaigns (Spanish, French, etc.).
What Changes When You Connect
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.
See it in action
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.
The honest tradeoffs
Assuming Simple Lookups Work
The user tries to guess the full name of 'MK' just based on context or uses a generic search that only returns vague geographical regions, forcing them to manually research the country.
Use the resolve_country tool. Pass the code ('MK') and let the MCP handle the ambiguity, guaranteeing you get North Macedonia plus its full set of codes.
Using Multiple Tools for One Task
The user connects a separate 'Get Alpha-3 Codes' tool, then another 'Get Full Name' tool, and has to stitch the data together in a spreadsheet. This is slow and error-prone.
Don't use multiple tools. resolve_country handles everything in one call: full name, alpha-3, numeric ID—all at once.
Ignoring Language Requirements
The user needs to run a Spanish campaign but forgets to specify the language when resolving codes. The resulting data uses default English names, causing localization errors.
Always include the optional language parameter in your prompt with resolve_country (e.g., asking for 'es' output) to ensure correct multilingual results.
When It Fits, When It Doesn't
Use this MCP if your workflow requires absolute data certainty regarding international location identifiers. If you need to convert a raw code into its full name, alpha-3, and numeric ID simultaneously, this is your tool. You absolutely must use it when dealing with CRM or Martech data from multiple continents.
Don't use this MCP if all you need is basic text processing (like cleaning up capitalization) or if you only care about one single piece of information (like just the name). For those limited tasks, a simpler string manipulation function will work fine. But when you cross borders and need to normalize data for multiple systems, resolve_country provides the necessary depth.
Questions you might have
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.
We've already built the connector for Country Data Resolver. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 1 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.