Summary
The map comes back drawn, not as a list of coordinates.
The static renderer works out the viewport itself and returns the route JSON with the image, so there is no separate calculation call. Where the client supports it, the interactive map draws several overlays at once — a route plus an isochrone plus the geofences — each in its own colour.
What it is
Magic Lane's own TypeScript server over its mapping and routing APIs. Eight tools covering search, routing, isochrones, reverse geocoding, geofences and two kinds of map rendering, over stdio or HTTP.
What you get
- Addresses, cities and points of interest found with category filters around a reference location — magiclane-location_search
- Routes across multiple waypoints with transport modes, POI stops along the way and multi-delivery optimisation — magiclane-route_planner
- Reachability polygons by time or distance for car, lorry, truck, pedestrian, bike or public transport — magiclane-isochrone_calculator
- Circular routes that return to where they started, for a run, a ride or a delivery loop — magiclane-round_trip
- Coordinates turned into addresses with the administrative hierarchy and nearby POIs — magiclane-reverse_geocode
- Geofences created as polygons, circles or rectangles, queried by id, bounding box or proximity, updated, deleted and point-tested — magiclane-geofence_manager
- A static map image of a route, isochrone, round trip or plain view as PNG, JPEG or WebP, with the route JSON alongside it — magiclane-static_map_render
- A pan-and-zoom vector map rendered inside the conversation, with one or many overlays each drawn in its own colour — magiclane-interactive_map
Requirements
Node.js 22 or newer and a Magic Lane API key in MAGICLANE_API_KEY. Run npx @magiclane/mcp-server for stdio, or the HTTP server for web and serverless clients. VERBOSE and HTTP_TIMEOUT_SECONDS, default 30, are optional. A Dockerfile is included.