Apogeoapi MCP Server

MCP server for ApogeoAPI — geographic data, live exchange rates & IP geolocation. The apogeoapi mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 9 defined tools rather than through you.

What it actually does

MCP (Model Context Protocol) server for ApogeoAPI — geographic data, live exchange rates, and IP geolocation for Claude Desktop, Cursor, and any MCP-compatible AI assistant.

Its toolset

Everything the assistant can do here goes through one of these:

• get_country — Full country data by ISO2/ISO3 code — name, capital, region, population, currency, live USD rate, timezones, phone code
• list_countries — Paginated list of all 250+ countries
• search_countries — Search countries by partial name
• get_states — All states/provinces for a country
• get_cities — All cities for a state by numeric state ID
• get_currency_rate — Live USD exchange rate for a country's currency (updated every 4 hours)
• geolocate_ip — Country, region, city, coordinates, timezone, and EU membership for any IPv4/IPv6
• global_search — Search across countries, states, and cities in one query
• Cursor — Add the same block under mcpServers in Cursor's MCP configuration file (~/.cursor/mcp.json)

Configuration

You will need 2 environment variables: APOGEOAPI_KEY, APOGEOAPI_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Apogeoapi MCP's toolset — get_country, list_countries, search_countries and 6 more — is a fair guide to whether it matches your workflow. It is maintained by apogeoapi; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Apogeoapi MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the apogeoapi mcp mcp server does with a few real requests.