bbox-mcp-server
Related Servers
Alternatives to bbox-mcp-server
No user-submitted related servers found.
Related Servers
AlicenseBqualityCmaintenanceEnables AI agents to become geospatially intelligent assistants with tools for location search, smart routing, round trip planning, reverse geocoding, isochrone analysis, route visualization, geofence management, and interactive map display.817 npm7Apache 2.0- AlicenseAqualityDmaintenanceGeospatial API tools for AI agents — geocoding, reverse geocoding, routing, isochrone, distance matrix, static maps, H3 hexagons, elevation, GPS map-matching, point-in-polygon, address normalisation, timezone lookup, and batch geocoding. Built on OpenStreetMap infrastructure. Cost-effective alternative to Google Maps API.1834 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides geographic coordinate geometry tools for computing midpoints, centroids, bounding boxes, and point-in-bbox tests, enabling spatial calculations via natural language queries.106 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides 15 geospatial utility tools for AI agents, covering coordinate transformation, spatial data validation, elevation/terrain, viewshed analysis, and drone flight planning.1MIT

Mapbox MCP Serverofficial
AlicenseAqualityBmaintenanceProvides geospatial intelligence to AI agents through Mapbox APIs, enabling geocoding, routing, POI search, map images, and offline spatial calculations.284,065 npm367MIT- FlicenseNot gradedqualityDmaintenanceAI agents hallucinate math. Euclid fixes that. Connect once and give your agent 10 deterministic tools: arithmetic, unit conversion, statistics, datetime, finance, regex, color, encoding, validation, and geospatial. Same input, same output, every time.2-
TDQS
Scored across 10 tools
Most tools target clearly distinct operations (geocoding, reverse geocoding, H3 indexing, routing, elevation, share URLs). The main overlap is between search_overpass and aggregate_overpass_h3, which share the same Overpass query surface and differ only by H3 binning, and spatial_calc bundles four disparate modes into one tool. Descriptions do enough to steer selection, but these boundaries are the weak spots.
Nine of ten names follow a predictable verb_noun pattern (get_h3_indices, get_bounds, search_overpass, list_osm_tags, calculate_route, get_elevation, generate_share_url). The exceptions are reverse_geocode (verb-first but noun-shaped) and spatial_calc (noun-only), both readable but minor deviations from the dominant convention.
Ten tools is well within the sweet spot and each one maps to a distinct geospatial capability. No tool feels redundant enough to remove, and the surface is not padded with trivial variants.
The surface covers the full stateless geospatial workflow: coordinate parsing/forward geocoding, reverse geocoding, tag discovery, POI search, density aggregation, H3 indexing, routing, elevation, offline geometry, and map sharing. Gaps are minor — no batch/bulk geocoding, isochrone/route-matrix operations, or explicit GeoJSON export are present, but agents can work around these via existing tools.