Radius search answers where can I fill up now; a trip needs a different question, and `calculate_route` handing its `geometry` to `find_route_stations` with a `corridor_km` width answers where can I fill up on the way. Everything downstream runs on coordinates, so `geocode` is the first call in nearly any chain, and the `fuel` filter sits on `find_nearest_stations`, `find_route_stations` and `get_stations_in_area` alike, which is what makes it usable when you need a specific grade rather than whatever is nearest.
A fuel-station lookup and routing server: 5 tools covering geocoding, driving-route calculation with waypoints, and station search by radius, by bounding box or along a route corridor, each search filterable by fuel type.
- Coordinates from a name: `geocode` searches for a location by `query` and takes `lat` and `lon` alongside it.
- A driving route between two points: `calculate_route` takes `origin_lat`, `origin_lon`, `dest_lat`, `dest_lon` and a list of `waypoints`, and returns the route between them.
- Stations near where you are: `find_nearest_stations` returns the stations closest to a `lat`/`lon`, bounded by `radius_km` and `limit` and narrowed to a `fuel` type.
- Stations along where you are going: `find_route_stations` takes a route `geometry` and a `corridor_km` width and returns the stations inside that corridor for a given `fuel`.
- Stations across an area rather than around a point: `get_stations_in_area` returns the stations inside a `bbox`, filtered by `fuel`.
No account and no key. Coordinates are what the station and routing calls run on, so a place name has to pass through `geocode` first. The server is GPL-3.0, which matters if you plan to redistribute a modified copy.
One command — npx -y pumperly-mcp