Geocode, reverse-geocode, autocomplete, route and search places. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the Geoapify connector, then ask in plain words. The AI picks the tools.
For developers, analysts and logistics planners who use Geoapify for geocoding, places and routing.
The AI converts an address or place name into coordinates and address parts, or coordinates into the nearest address. It can also suggest addresses for a partial query.
The AI searches places by category within an area, optionally filtered by name, for example cafes near a square. It can open place details by place id.
The AI computes a route between waypoints for a travel mode and returns the distance, time and legs. You can compare modes such as driving and walking.
The AI computes an isoline from a point with a time or distance budget. It shows what area you can reach, for example for a delivery zone.
The AI reads the country, city and coordinates for an IP address. The result is approximate.
The login page asks for your Geoapify API key.
Create one in Geoapify → Settings → API. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"geoapify": {
"url": "https://geoapify.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"geoapify": {
"type": "http",
"url": "https://geoapify.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Geoapify API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+ | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this Geoapify server only. Ask your AI to run geoapify_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with geoapify_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with geoapify_upgrade before then undoes the cancel. Or write to [email protected].
geoapify_geocode_searchgeoapify_geocode_reversegeoapify_geocode_autocompletegeoapify_placesgeoapify_place_detailsgeoapify_routinggeoapify_isolinegeoapify_ip_geolocationgeoapify_usage_statusgeoapify_request_featuregeoapify_upgradegeoapify_cancel_subscriptionTurn addresses into coordinates and back. Find places of a category in an area. Get the route, distance and travel time between points. Find the area reachable within a time or distance. Look up the approximate location of an IP address. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Geoapify. The server calls the Geoapify API with your own Geoapify access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Geoapify API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Geoapify API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Geoapify API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Geoapify.
All 8 Geoapify tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Geoapify server only. Cancel any time: your paid plan then runs to the end of the paid period. Run geoapify_usage_status to see how many calls you used.
Ask the AI to run geoapify_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run geoapify_cancel_subscription. Your paid plan continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with geoapify_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
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.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.