Apogeoapi Mcp
Give agents authoritative country, city, IP geolocation, and FX data while you build localized or pricing-aware features.
Overview
com.apogeoapi/apogeoapi-mcp is an MCP server for the Build phase that exposes Apogeo geographic and FX reference data through npm stdio tools.
What is this MCP server?
- 250+ countries and 150K+ cities via Apogeo API
- 161 live foreign-exchange rates for multi-currency displays
- IP geolocation tools for signup defaults and fraud heuristics
- stdio npm package @apogeoapi/mcp (v1.0.2) with APOGEOAPI_KEY
- Free tier cited: 1,000 requests/month at app.apogeoapi.com
- 250+ countries coverage
- 150K+ cities in catalog
- 161 live FX rates
What problem does it solve?
Agents and early backends guess at country lists, city metadata, IP location, and exchange rates when builders lack a single geodata source in the dev loop.
Who is it for?
Indie SaaS and mobile apps that need quick country/city pickers, IP-based defaults, or live FX without integrating a full maps platform first.
Skip if: Products requiring turn-by-turn routing, custom polygon geofencing, or deep historical macro datasets outside Apogeo’s scope.
What do I get? / Deliverables
With APOGEOAPI_KEY configured, your agent can pull normalized geo and FX facts into code, configs, and API stubs during implementation.
- Agent-fetched country and city records for seed data and UI
- IP geolocation answers for defaults and analytics stubs
- Live FX rate snippets for multi-currency prototypes
Recommended MCP Servers
Journey fit
Reference geo and currency APIs belong on the build backend shelf when implementations need consistent location and money metadata during coding. Backend covers MCP tools that supply lookup services your API routes, signup flows, or billing logic will call.
How it compares
Reference geodata and FX MCP over Apogeo API, not a self-hosted PostGIS skill or general-purpose weather MCP.
Common Questions / FAQ
Who is com.apogeoapi/apogeoapi-mcp for?
It is for solo developers wiring localization, geolocation, or currency features who want agents to query Apogeo during backend and prototype work.
When should I use com.apogeoapi/apogeoapi-mcp?
Use it while building APIs, signup flows, or pricing UI that need country/city lists, IP geolocation, or live FX rates in the agent session.
How do I add com.apogeoapi/apogeoapi-mcp to my agent?
Run npx with package @apogeoapi/mcp per the server manifest, set environment variable APOGEOAPI_KEY from https://app.apogeoapi.com, and register the stdio server in your MCP client.