Geowire MCP Server

Connect Geowire to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Unified place search for OpenStreetMap, Google & your own data. Fallback, merge, zero API keys. The geowire mcp server is what makes that connection.

What the server does

GeoWire is an open-source geo intelligence gateway that sits between AI agents and map/place data providers (OpenStreetMap, Google, Yelp, Foursquare, US Census, your own data) and exposes them through a single MCP server, REST API, and SDK. One interface for place search, geocoding, directions & distance matrices, and commercial-area analysis (density, ratings, demographics) — with provider fallback, multi-provider merge + dedup, cost budgets, and a policy engine that enforces each provider's caching/attribution terms.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• search_places — Natural-language + coordinate/region place search
• get_place — Details by provider:providerPlaceId reference
• geocode_address — Address → coordinates (+ normalized address)
• reverse_geocode — Coordinates → nearest address
• get_directions — Route between waypoints (distance, time, legs) — no key (OSRM)
• distance_matrix — N×M travel distances/times — rank candidates by drive time — no key
• analyze_area — Commercial-area analysis: category density, competition, rating landscape, demographics
• get_isochrone — Travel-time reachability polygon ("what's within a 15-min drive") — no key (OSRM)
• get_demographics — Population / age / income for a coordinate's area (US Census, free key)
• list_geo_providers — Active providers, capabilities, status (agent self-awareness)

Credentials and setup notes

Configuration is passed through the environment: GOOGLE_MAPS_API_KEY, YELP_API_KEY, CENSUS_API_KEY, KAKAO_REST_API_KEY, NAVER_CLIENT_ID, NAVER_CLIENT_SECRET, FOURSQUARE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

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. Geowire's toolset — search_places, get_place, geocode_address and 7 more — is a fair guide to whether it matches your workflow. It is maintained by geowire; 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.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Geowire.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.