Summary
Two tools, no key, OpenStreetMap underneath.
Geocoding is usually the piece that drags an API key and a billing account into a project; this needs neither. The data is OpenStreetMap's, which is excellent in some places and thin in others — worth a spot check against addresses you already know before you build on it.
What it is
A two-tool geocoding server over the Nominatim API. Forward geocoding takes a free-form or structured description and returns a coordinate; reverse geocoding takes a latitude and longitude and returns the address of the closest suitable OpenStreetMap object.
What you get
- A coordinate from an address, given either as free text or as structured fields
- An address from a latitude and longitude, resolved to the nearest suitable OpenStreetMap object
Requirements
Node. No account, no key — it runs against Nominatim, the OpenStreetMap search service.
Setup effort
One command — npx -y @geocoding-ai/mcp