Geoapify vs MCP Server
A side-by-side look at the Geoapify and MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Geoapify for location services work as a local process; choose MCP Server for location services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Geoapify when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You want tools like
geocode, reverse_geocode, places.
Choose MCP Server when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
STHAN_API_KEY. - You want tools like
sthan_verify_address, sthan_parse_address, sthan_autocomplete_address.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 59/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | STHAN_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 4 | 8 |
| Full listing | View Geoapify | View MCP Server |
Tools & capabilities
Geoapify tools 4
geocodeForward 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. Example: geocode({ text: "1600 Amphitheatre Parkway, Mountain View, CA" })reverse_geocodeReverse 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.2945 })placesSearch 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: "catering.restaurant", lat: 48.8584, lon: 2.2945, radius: 1000 })routingRouting / 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, from_lon: 2.2945, to_lat: 48.8606, to_lon: 2.3376, mode: "drive" })
MCP Server tools 8
sthan_verify_addressVerify a US address is real and deliverable. Returns standardized format, ZIP+4, DPV, residential/commercial.sthan_parse_addressParse freeform US address text into structured components (street number, name, type, direction, unit, city, state, zip).sthan_autocomplete_addressSuggest complete US addresses from partial input. Sub-100ms.sthan_autocomplete_citySuggest US cities from partial input, with state code.sthan_autocomplete_zipcodeSuggest US ZIP codes from partial input.sthan_geocodeUS address → latitude/longitude with accuracy + confidence, county, ZIP+4 and time zone.sthan_reverse_geocodeLatitude/longitude → nearest US street address with distance in meters, county, ZIP+4 and time zone; `limit` (up to 10) also lists nearby addresses.sthan_ip_geolocationIPv4 or IPv6 → location (country to postal code, local time, flag, currency), the network behind it (ASN, ISP, proxy/hosting flags) and a confidence score.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Geoapify
{
"mcpServers": {
"geoapify": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-geoapify"
]
}
}
}
MCP Server
{
"mcpServers": {
"sthan-io-mcp-server": {
"command": "npx",
"args": [
"-y",
"@sthan/mcp-server"
],
"env": {
"STHAN_API_KEY": "YOUR_STHAN_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Geoapify is categorized under Location Services and uses a local stdio subprocess. MCP Server belongs to Location Services and uses a local stdio subprocess. Pick Geoapify for location services work and MCP Server for location services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Geoapify has no declared pricing — check the project's own site. MCP Server is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add geoapify and sthan-io-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Geoapify has a quality signal of 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. MCP Server has 61/100 (Good) with 5 views, 0 installs and 0 GitHub stars.