Supercharge your AI with REST Countries Alternative. Query Global Country Data By Any Attribute.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
REST Countries Alternative MCP Server accesses global data points for any nation, including capitals, currencies, languages, and political status. This server lets your agent query geographic and economic facts using natural language prompts.
You can filter countries by continent (`filter_by_region`), find nations based on their currency or official code, or search results using translated names.
It's a powerful reference layer for geo-data.
What your AI can do
Get all countries
Retrieves information for all countries in the database; you must specify which 10 fields you want.
Search by capital
Finds countries based on a known capital city name.
Search by code
Searches for country data using its standard national code (like 'USA').
Use filter_by_independent to narrow down lists of nations based on their current independence designation.
Limit search results using filter_by_region and filter_by_subregion to focus only on specific geographical clusters (e.g., Oceania, Northern Europe).
Run search_by_codes to retrieve data for several nations simultaneously using their ISO codes.
Execute targeted searches, such as finding all countries that use the Euro or speaking Mandarin Chinese, using tools like search_by_currency or search_by_language.
Run get_all_countries to pull metadata for every nation in the database. You must specify exactly which fields you want (up to 10) to avoid errors.
Ask an AI about this
Compatible AI Apps
OAuth 2.0 Compatible Gemini Waiting for input…
REST Countries Alternative: 12 Tools for Geo-Data Retrieval
Use these tools to filter, search, and retrieve specific metadata about countries using their codes, names, regions, or currencies.
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 REST Countries on VinkiusGet All Countries
Retrieves information for all countries in the database; you must specify which 10 fields you want.
Search By Capital
Finds countries based on a known capital city name.
Search By Code
Searches for country data using its standard national code (like 'USA').
Search By Codes
Retrieves data for multiple countries at once by providing a list of their codes.
Search By Currency
Finds all countries that use a specific currency, given its name or code (e.g....
Search By Demonym
Searches for countries based on the common name of their citizens (the demonym).
Filter By Independent
Narrows down search results to include only nations that are marked as independent.
Search By Language
Locates countries using a specific language, given its code or full name.
Search By Name
Finds countries by their common official name (e.g., 'Canada').
Filter By Region
Limits the dataset to countries located within a major continent (e.g., Africa...
Filter By Subregion
Further narrows results by specific geographic subregions (e.g., Northern Europe...
Search By Translation
Searches for a country using its translated or alternate name in another language.
Connect to your AI in seconds. 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.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token from
cloud.vinkius.com. For OAuth-protected servers, expand Advanced
settings to add credentials.
Start a conversation
Open a new chat. The REST Countries Alternative integration is available immediately — no restart needed.
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 REST Countries, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ 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 REST 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 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Dealing with messy data sets that mix codes, names, and translations is tedious.
Today, when you pull country data from multiple sources, you're constantly cross-referencing: Does this list use the common name ('China')? The official code (CHN)? Or a translated variant in Japanese? You end up writing messy scripts just to normalize the inputs.
With the REST Countries Alternative MCP Server, your agent handles that mess. Instead of manually checking every input against multiple APIs, you simply prompt it: 'Give me all countries that use this language.' The system runs `search_by_language` and pulls clean results, eliminating manual data cleanup.
The REST Countries Alternative MCP Server gives you facts about any nation's attributes.
You don't have to run dozens of calls just to check a single country. You can combine `search_by_capital` and `filter_by_subregion` in one conversation thread. The agent handles the logic, making sure your query is both accurate and efficient.
The difference now is speed and reliability. You get clean, verified data points instantly—no more juggling multiple APIs or fighting ambiguous input parameters.
What your AI can actually do with this
You're connecting your AI agent to a massive global database using this MCP server, and it handles all the tricky country data for you. Your client can pull specific geographic, economic, or political facts about any nation without needing dozens of separate API calls. You just talk to it like you'd talk to me on the corner—it’ll figure out what you want.
Filtering Data Down to What Matters
Filtering is where this thing shines. If you only care about a specific type of country, you can narrow the results immediately. To check political status, use filter_by_independent to pull lists containing only nations designated as independent. For geography, you've got options: you can limit your search using filter_by_region for major continental groups like Asia or Africa.
If that’s too broad, you can drill down further by calling filter_by_subregion, which lets you focus on specific clusters, say, Oceania or Latin America.
Targeted Searches and Deep Queries
Need to find something specific? You don't have to guess. The server gives you several ways to zero in on data points. If you know a capital city name, use search_by_capital to pull up the corresponding country records. Want to check a nation by its standard code—like 'USA'? Just pass that through search_by_code.
It’s also got tools for broader searches: run search_by_name to look up countries using their common official name, or if you're dealing with alternate names, use search_by_translation to find a country by its translated title in another language.
To pull data based on demographics or culture, your agent can search for nations that speak a specific language using search_by_language, or locate countries by their common citizen name—what they call the demonym—with search_by_demonym. If you're tracking trade or currency, use search_by_currency to find every country that uses a certain money type (like 'EUR').
You can also pull up nations using an ISO code through search_by_codes, which lets your agent retrieve data for multiple countries in one go.
Bulk and Comprehensive Data Retrieval
When you need the whole picture, this server delivers. If you want to map out every nation available, run get_all_countries. Keep this in mind: you gotta specify exactly which 10 fields you want when running that tool; otherwise, it'll throw an error for sure. When your query needs data from multiple sources at once—say, finding a country by both its code and its currency—you can combine calls using search_by_codes to handle several nations simultaneously.
This setup means you don’t need five different APIs; you just send one prompt through your AI client. It runs the necessary tool, pulls the specific data set, and hands it back formatted and ready to use.
019e38e4-2986-7063-ae96-ea237a9f2bd9 
Here's how it actually works
The bottom line is: You ask for world facts in plain English, and the server runs the specific API calls needed to deliver the answer.
Subscribe to the REST Countries Alternative server and connect your AI client.
Prompt your agent with a natural language query (e.g., 'What countries use the Yen?').
The agent executes one or more tools—like search_by_currency—and presents you with the structured data.
Who is this actually for?
Data Analysts who need quick metadata validation; Developers building geo-aware applications that can't rely on static data sets. It’s for anyone tired of switching between a database and an API documentation page just to verify a country code or currency format.
Gathering background metadata—like finding the capital city alongside population data, or checking which languages are spoken in specific regions for a report.
Needing to verify ISO 3166-1 codes, currency formats, and official language mappings without leaving their IDE. They use tools like search_by_code constantly.
Pulling comparative data for a paper—for instance, comparing economic indicators between countries in the 'South America' subregion.
What Changes When You Connect
Get granular detail by using search_by_capital. Instead of guessing, you simply tell your agent the capital city and get back the full country profile.
Don't manually check codes. Use search_by_codes to pull data for five different countries in one call. It saves time when comparing multiple nations.
Need a regional breakdown? Combine filter_by_region (to narrow it down) with filter_by_subregion (for precision). This lets you analyze geographic groups without messy manual filtering.
Verify languages and money sources instantly. Tools like search_by_currency let you check which countries use the Yen or Euro, eliminating guesswork in financial modeling.
Handle name variations easily. If a country is called 'Brazil' in one place but has an official translated name elsewhere, search_by_translation finds it for you.
See it in action
Checking trade partners by currency.
A financial analyst needs to list all countries that accept the Brazilian Real (BRL). They ask their agent, which uses search_by_currency. The agent returns a clean list of nations and their respective codes, allowing the analyst to immediately cross-reference this data in a spreadsheet.
Mapping regional political boundaries.
A geopolitical consultant needs to compare three specific states: one from Northern Europe and two from South America. They use filter_by_subregion twice, combined with the general search tools, ensuring they only pull data for countries that are also marked as independent via filter_by_independent.
Validating a client list of country codes.
A developer gets a spreadsheet full of ambiguous 3-letter codes. Rather than hitting the API twelve times, they use search_by_codes. This tool runs once and confirms which countries are valid, flagging any bad data points immediately.
Building an educational quiz on global facts.
An educator needs to generate questions that test knowledge of both language and capital. They use search_by_language (to find all countries using Arabic) and then pair the results with search_by_capital to pull a list of unique capitals for the quiz.
The honest tradeoffs
Using general searches only
Asking 'Tell me about countries' and getting a massive, unstructured dump of data that includes everything you don't need.
Don't use generic prompts. Be specific: Use search_by_language first, then apply filter_by_region to restrict the results. This tightens your search parameters immediately.
Mixing up country codes and names
Trying to search for 'China' using a code that actually belongs to Vietnam, resulting in zero or incorrect data.
If you have the official 3-letter code, use search_by_code. If you only know the name, stick to search_by_name until you confirm the code.
Overlooking regional limitations
Asking for countries in 'South America' but getting results from North America because they didn't filter by subregion.
Always use filter_by_subregion when you know the specific area. If you just know the continent, start with filter_by_region.
When It Fits, When It Doesn't
Use this server if your goal is structured data validation and comparative analysis across many nations. You need to answer 'What country has X attribute?' or 'Which countries have both Y and Z?'. This means using specialized tools like search_by_currency combined with filter_by_subregion. Don't use this if you are trying to write a narrative report that requires subjective analysis (e.g., 'Why is Brazil successful?'). For those tasks, your agent needs external knowledge or LLM reasoning; the server only provides facts. If you simply need to look up one country’s name and capital, while search_by_name works, it's better practice to use a direct lookup tool if available to keep calls minimal.
Questions you might have
How do I find countries by their continent? +
You use filter_by_region. Just tell your agent which region you want (e.g., 'Asia') and it filters the data for you.
Can I search for multiple countries using the search_by_codes tool? +
Yes, use search_by_codes. This function lets you input a list of codes (e.g., ['USA', 'CAN']) and get data back for every country in that batch.
What if the name I use is translated? +
Don't worry about translations; use search_by_translation. It finds countries even when you provide their alternate or foreign-language names.
Do I need to specify fields when calling get_all_countries? +
Yes, you must. The tool requires you to list the specific 10 fields (like 'population' and 'currency') you actually want back to prevent a bad API request.
Does running a query using the `search_by_name` tool require an API key or token? +
No, you don't need to worry about tokens. This is a public API, so no specific credential is required. If the server prompts for authentication, enter 'public'.
What happens if I run `get_all_countries` without specifying fields? +
The request will fail with a 400 Bad Request error. You must specify which data points you need—you can select up to ten specific fields.
Can the `search_by_currency` tool handle both codes and full names? +
Yes, it supports both methods. You can search by a standard three-letter code (like EUR) or by typing out the currency's full name.
How do I use `search_by_demonym` to find country data? +
You simply ask your agent for the demonym. The tool searches for countries that share a specific common designation among their citizens.
How do I retrieve a list of all countries with specific data points? +
Use the get_all_countries tool. You must provide a comma-separated list in the fields parameter (e.g., 'name,capital,population') to specify exactly which information you want to receive.
Can I find countries based on the currency they use? +
Yes! Use the search_by_currency tool and provide the currency name or code (like 'euro' or 'USD'). The agent will return all countries where that currency is legal tender.
Is it possible to filter countries by their geographic region? +
Absolutely. Use the filter_by_region tool with values like 'Europe', 'Americas', 'Asia', 'Africa', or 'Oceania' to get a list of countries in that specific part of the world.
We've already built the connector for REST Countries Alternative. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting.
You're up and running in seconds.
Gemini 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.