Geoapify MCP — wraps the Geoapify Location Platform (geoapify.com)
If you already use MCP, the mcp mcp server is the piece that lets your assistant work with it directly. Geoapify MCP — wraps the Geoapify Location Platform (geoapify.com).
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
geocode — Forward geocoding: convert an address, place name, or freeform location text into geographic coordinates (latitude/longitude). Returns matchedreverse_geocode — Reverse geocoding: convert latitude/longitude coordinates into the nearest street address. Returns formatted address, country, city, street, houseplaces — Search for places and points of interest (POI) near a location, filtered by Geoapify category. Returns name, formatted address, categories, lat, lonrouting — Routing / directions: compute the distance and travel time between two points for a given travel mode (drive, walk, bicycle, transit). ReturnsSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
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. MCP's toolset — geocode, reverse_geocode, places and 1 more — is a fair guide to whether it matches your workflow. It is maintained by mojibake-ai; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| geocode | Forward geocoding: convert an address, place name, or freeform location text into geographic coordinates (latitude/longitude). Returns matched candidates with formatted address, lat, lon, country, city, and postcode. Exa |
| reverse_geocode | Reverse geocoding: convert latitude/longitude coordinates into the nearest street address. Returns formatted address, country, city, street, house number, and postcode. Example: reverse_geocode({ lat: 48.8584, lon: 2.294 |
| places | Search for places and points of interest (POI) near a location, filtered by Geoapify category. Returns name, formatted address, categories, lat, lon, and distance from the center point. Example: places({ categories: "cat |
| routing | Routing / directions: compute the distance and travel time between two points for a given travel mode (drive, walk, bicycle, transit). Returns distance in meters and time in seconds. Example: routing({ from_lat: 48.8584, |
{
"mcpServers": {
"geoapify": {
"url": "https://gateway.pipeworx.io/geoapify/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.