Geoapify MCP server. Geocode, reverse-geocode, autocomplete, route and search places.
Add to your MCP config, then reload & authorize:
{
"mcpServers": {
"geoapify": {
"url": "https://geoapify.usefulapi.io/mcp"
}
}
}| Tool | Type | What it does |
|---|---|---|
geoapify_geocode_search | read | Forward geocoding Forward geocoding — turn a free-form address or place name into coordinates and structured address parts. Geoapify REST: GET /v1/geocode/search. |
geoapify_geocode_reverse | read | Reverse geocoding Reverse geocoding — turn coordinates into the nearest address / place. Geoapify REST: GET /v1/geocode/reverse. |
geoapify_geocode_autocomplete | read | Address autocomplete Address autocomplete — suggest completed addresses/places for a partial query, ideal for as-you-type inputs. Geoapify REST: GET /v1/geocode/autocomplete. |
geoapify_places | read | Places search Search for places (POIs) by category within an area, optionally filtered by name/conditions. Returns a GeoJSON FeatureCollection. Geoapify REST: GET /v2/places. |
geoapify_place_details | read | Place details Get detailed information (and optionally geometry/features) for a place. Provide either `id` (the `place_id` returned by geoapify_places) OR both `lat` and `lon`. Geoapify REST: GET /v2/place-details. |
geoapify_routing | read | Routing Compute a route between waypoints for a travel mode, returning distance, time and legs. Geoapify REST: GET /v1/routing. |
geoapify_isoline | read | Reachability isoline Compute a reachability isoline (isochrone/isodistance) — the area reachable from a point within a time or distance budget. Geoapify REST: GET /v1/isoline. |
geoapify_ip_geolocation | read | IP geolocation Look up the approximate location (country, city, coordinates) of an IP address. Geoapify REST: GET /v1/ipinfo. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.