Geo vs Geoapify

A side-by-side look at the Geo and Geoapify MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

G
GeoLocation Services
Geocoding, truck routing, traffic, weather, and place search via MCP — 11 hosted tools.37FairAuth: not declared
Geoapify logoGeoapifyLocation Services · Local subprocess (stdio)Geoapify MCP — wraps the Geoapify Location Platform (geoapify.com)59GoodAuth: not declared

Verdict: choose Geo for location services work; choose Geoapify 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?

G
Choose Geo when

  • You need dedicated capabilities in the Location Services domain.
Explore Geo

Geoapify logoChoose 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.
Explore Geoapify

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
G
Geo
Geoapify logoGeoapify
CategoryLocation ServicesLocation Services
Quality signal37/100 · Fair59/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—0
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listed4

Tools & capabilities

Geo tools

No tool names declared yet. Check the project README from the listing page.

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" })

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.

Geo

No confirmed install command for Geo yet — follow the setup steps linked from its listing page rather than a guessed package name.

Geoapify

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "geoapify": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-geoapify"
      ]
    }
  }
}

Frequently asked questions

Geo is categorized under Location Services and uses an install path we have not confirmed yet. Geoapify belongs to Location Services and uses a local stdio subprocess. Pick Geo for location services work and Geoapify 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. Geo has no confirmed install command yet — follow its own setup instructions.

Geo has no declared pricing — check the project's own site. Geoapify has no declared pricing — check the project's own site. 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 geo and geoapify as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Geo has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Geoapify has 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars.