PlaceRoot
Related Servers
Alternatives to PlaceRoot
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server providing structured access to OpenStreetMap data through Overpass and Nominatim APIs, enabling geocoding, nearby place searches, element queries, and tag counting without API keys.7MIT
- AlicenseNot gradedqualityBmaintenanceFree geospatial MCP server for AI agents, providing geocoding, reverse geocoding, POI search, and route planning using OpenStreetMap data via Nominatim, Overpass, and OSRM.GPL 3.0
- AlicenseAqualityFmaintenanceAn MCP server providing geocoding and place discovery services via Nominatim and OpenStreetMap. It enables users to perform forward and reverse geocoding, extract bounding boxes, and find nearby places or administrative hierarchies.10Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that provides AI agents with geospatial analytics by querying Overture Maps data directly from S3, enabling place analytics, building composition, land use classification, and transportation analysis.135MIT
- AlicenseAqualityAmaintenanceA read-only MCP server for OpenStreetMap offering geocoding, routing, route optimization, isochrones, and POI search—requiring no API key and built for AI travel planning.11476 npm5MIT
- AlicenseBqualityDmaintenanceA comprehensive MCP server providing 30 tools for geocoding, routing, and OpenStreetMap data analysis. It enables AI assistants to search for locations, calculate travel routes, and perform quality assurance checks on map data.30476 npm5MIT
TDQS
Scored across 48 tools
Multiple tools overlap heavily: find_near is explicitly a thin alias of find_places(where=..., category=...), from_to duplicates route with a walk default, and geocode/geocode_batch/geocode_address/geocode_intersection/reverse_geocode/resolve_place all sit in the same geocoding space with subtle boundaries (city granularity vs doorway vs intersection vs free-text GERS resolution). distance_matrix vs travel_time_matrix vs route vs compare_modes vs meeting_point all return pairwise travel numbers with only mode/model differences.
Names are almost uniformly snake_case with a predictable verb_noun or noun_at pattern (geocode_address, reverse_geocode, buildings_at, water_near, land_use_at). A few deviate (ground_location, compare_modes, gers_lookup, place_details) and some are noun-only, but style is consistent and readable.
48 tools is heavy for any single server and hard for an agent to select from reliably; several are explicitly redundant aliases (find_near, from_to) that inflate the count. A server this broad should be split into themed sub-servers rather than exposing ~50 near-overlapping entry points.
Coverage is genuinely broad: forward/reverse geocoding, divisions, places, routing, isochrones, matrices, buildings, water, transit, land use, diffing across releases, geometry ops, map rendering, and cache warming. Missing pieces are minor (no polygon/division listing by id, no explicit open-now since data lacks it), and the surface covers the stated 'location grounding' domain well.