The value is in the pairing: geocoding alone gives you coordinates, routing alone needs coordinates you do not have, and together they answer the question people actually ask. Both sit behind the `ai.model.base.url` property, so pointing it at your own pgGeocoder and pgrServer deployment is the supported path for anything beyond trying it out. Address coverage is Japanese, which is the geocoder's scope rather than a limitation of this server.
A Java MCP server that fronts two open-source geospatial services: pgGeocoder for Japanese address geocoding, and pgrServer for routing. That combination lets a model turn addresses into coordinates and then ask what the drive between them looks like, in one conversation.
- Geocoding a Japanese address into coordinates
- Reverse geocoding a latitude and longitude pair back into address information
- Driving distance between two coordinates, from a Dijkstra shortest-path search
- The path itself, not just the distance, so a route can be described rather than only measured
- Chained questions in a single prompt — look up two store addresses, geocode both, then get the driving distance between them
JDK 17 or newer, and the downloaded `mcpLocation.jar`. The client launches it with `java -jar` and a set of system properties: `-Dspring.ai.mcp.server.stdio=true`, `-Dspring.main.web-application-type=none`, an empty console logging pattern so the stdio channel stays clean, and `-Dai.model.base.url` pointing at the geocoding and routing host. Building from source is `mvn clean install`.