@pipeworx/overpass

Connect: https://gateway.pipeworx.io/overpass/mcp · Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 3

OpenStreetMap Overpass API MCP — programmatic OSM queries, no auth.

Tools

• query(qql) — raw Overpass QL for advanced queries.
• pois_near(latitude, longitude, tag, radius_m?, limit?) — POIs in a radius.
• places_in_bbox(south, west, north, east, tag, limit?) — POIs in a bounding box.

Data source

https://overpass.kumi.systems/api/interpreter — POST Overpass QL, returns JSON.

kumi.systems is the PRIMARY, not the better-known overpass-api.de, and the order is measured (fleet #2036, 2026-09-15): overpass-api.de returns a 406 to every request we can make from our egress — both Accept values, no Accept, no User-Agent, and a bare GET /api/status — while returning 200 to all of them from a residential address. An IP block wearing a 406; no header or proxy hop recovers it. overpass-api.de is kept as the fallback, and a primary that refuses OR hangs falls through to it.

Tools

• query — Run a raw Overpass QL query against OpenStreetMap. Use for complex spatial queries the helper tools can’t express. Example: `[out:json][timeout:25]; area[“name”=“Berlin”][admin_level=4]->.a; node[“ame
• pois_near — Find OpenStreetMap points of interest (shops, amenities, businesses) near a location. Give a location either as latitude+longitude OR as a place name via “place” (e.g. place: “Göttingen, Germany” — au
• places_in_bbox — Find OSM POIs inside a bounding box. Use for “every park in this area” or “all restaurants in this neighborhood”. Bounding box is (south, west, north, east) in degrees.