Categories › Knowledge & Everyday › Maps, travel & weather
Maps for agents: truck/ADR routing, geocoding, places, matrices, isochrones, EV and fleet planning.
Remote server: your requests and data go to mcp.mapmap.ai. Claude Code: claude mcp add --transport http mapmap https://mcp.mapmap.ai/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
camera_incidents — Road incidents a TRAFFIC CAMERA SAW and a vision model CONFIRMED, in force now: near a point (`near` [lat, lon] with `radius_m`, default 100cheapest_charging_along_route — Find the best EV charge points along a route, with the REAL extra travel time of stopping at each one, never a straight-line guess. Provide cheapest_fuel_along_route — Find the cheapest fuel along a route, with the REAL extra travel time of stopping at each station, never a straight-line guess. Provide `oricheck_adr_tunnel — Check whether a vehicle may pass through a tunnel of a given ADR category ("A"–"E"). Provide `hazmat` and, when known, the load's ADR 8.6.4 check_clearance_on_route — Measure a vehicle's overhead clearance along a route against surveyed point cloud geometry, wherever survey coverage exists. Routes with trucheck_style_contrast — Audit a map style's colour contrast against WCAG 2.1 (4.5:1 for label text, 3:1 for graphics like the route line), across both the light andcluster — Group stops into balanced geographic clusters, so a day too large for one optimisation can be optimised one cluster at a time. This is the fcoverage_guidance — Turn-by-turn guidance for one drive of a finished coverage plan (`submit_optimise_job` with `kind: "coverage"`, read with `get_job`), in onecreate_style — Create a hosted map style. Provide a name, optionally a named `base` to start from (light, dark, streets, midnight, navigator-day, navigatorelevation — Sample terrain elevation. Provide `points` (a bare list of coordinates) for point elevation, or `encoded_polyline` (optionally with `resamplevents_in_area — Earthquakes, volcano alerts and satellite fire detections in a bounding box, for display. Pass `bbox` [west, south, east, north] (WGS84), opgeo_area — Area in square metres enclosed by a ring of 3+ coordinates, computed geodesically. Always positive: the answer does not depend on whether thgeo_bbox — The axis-aligned bounding box enclosing 1+ coordinates, as {min_lat, min_lon, max_lat, max_lon}. Useful for fitting a map view to a set of sgeo_bearing — Initial bearing from one coordinate to another, in degrees clockwise from true north (0-360). This is the bearing at the START of the geodesgeo_centroid — The centroid (geometric mean position) of 1+ coordinates, e.g. to pick a depot location or centre a map. Local computation: no network call,geo_destination — The coordinate reached by travelling `distance_m` metres from `from` on `bearing_deg` (degrees clockwise from true north). The inverse of `ggeo_distance — Distance in metres between two coordinates. Computed geodesically on the WGS84 ellipsoid, so it is the straight-line (as-the-crow-flies) disgeo_length — Total length in metres of a polyline through 2+ coordinates, summed geodesically. This measures the line you supply, NOT a driven route , usgeo_nearest_point_on_line — The closest position on a polyline to a given coordinate, plus the geodesic distance to it in metres. The answer may lie between vertices, ngeo_point_in_polygon — Whether a coordinate lies inside a polygon: delivery zones, catchments, congestion or clean-air zones, site boundaries. Provide `point` {latgeo_simplify — Reduce the number of coordinates in a polyline while keeping its shape (Douglas-Peucker). `tolerance_deg` is in DEGREES, not metres: about 0geocode — Turn a place (address, POI, town) into coordinates. Ask two ways, and they combine: `query` is free text, one run-together string, the way aget_job — Read an asynchronous job submitted with `submit_optimise_job`: its status, and once it has finished, its result inline, exactly the body theget_style — Fetch a hosted style's latest theme document (the editable source) and the URL of its latest compiled MapLibre style. Use the theme to inspeget_usage — Check what your own API key has spent, so you can decide mid-task whether to keep going. Reading it is free: it costs no quota. Optional `frheritage_narration — Three to five short spoken lines an hour about the ground a route is on: one sentence, at the point the driver reaches the thing it is aboutlist_place_categories — List the canonical place categories you can pass as `category` to `nearby_places` and `search_along_route` (and browse on with `geocode`). Elist_style_layers — List everything a MapMap style theme can style: the first-party named bases a style can start from (pass one as `create_style`'s `base`, or match_trace — Snap a recorded GPS trace to the road network and say what it actually travelled over. Provide `shape` (2 to 2000 recorded points, oldest fimatrix — Compute a travel time/distance matrix between origins (rows) and destinations (columns). Costing "auto", "truck" (with optional `truck` profnearby_places — Find places near a point, nearest first with distance in metres, by category (cafes, fuel, EV charging, parking), by name or brand ("the neanearby_stops — England bus and coach stops near a point, nearest first. Pass `lat` and `lon` (WGS84), optional `radius_m` (1 to 2,000, default 500) and `linext_departures — Timetabled bus departures at one stop, from the Bus Open Data (BODS) timetables. Pass `stop` (the NaPTAN ATCO code `nearby_stops` returns), optimise_routes — Optimise multi-vehicle, multi-stop delivery plans (VRP). Provide `vehicles` (id, start/end, capacity, skills, time_window), `jobs` (id, locaorder_stops — Put a single run's stops in the best visiting order ("order my errands"). Provide `start` {lat, lon} and `stops` (1-100 entries of {locationplaces_in_view — What is over THERE: given a position and the direction the user is facing, the places inside that cone, and whether the ground and the buildplan_day — Turn an itinerary into one navigable multi-stop route. Provide a `start` and `stops` (each a `location` {lat, lon} or a free-text `name` to plan_errands — Order a handful of errands against a hard arrival time, and say honestly whether they fit. This is the "pick up a prescription, get petrol, plan_ev_route — Plan a whole electric-vehicle journey, charge stops included. Give `origin` and `destination` (plus optional `waypoints`) and a `vehicle`, areachable_area — Compute the area reachable from an origin within one or more travel-time budgets, walkability/cyclability rings. Costing "pedestrian" answerNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.