OSM Edit MCP Server
Related Servers
Alternatives to OSM Edit 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 npm8Apache 2.0- AlicenseAqualityDmaintenanceProvides location-based services and geospatial data from OpenStreetMap, enabling geocoding, route directions, nearby place search, and neighborhood analysis through natural language.12MIT
- AlicenseAqualityCmaintenanceEnables LLMs to geocode and reverse geocode places, find nearby points of interest, search categories within an area, get turn-by-turn routing, suggest meeting points, and analyze neighborhoods, commutes, schools, EV charging, and parking through OpenStreetMap data services. It also serves place and map tile resources over stdio, SSE, or Streamable HTTP transports.12MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to find nearby public places such as pharmacies, supermarkets, gas stations, EV chargers, libraries, and post offices, with attributed opening-hours data from OpenStreetMap.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access Mapbox location services for geocoding, POI search, multi-modal routing, travel time analysis, isochrones, map matching, and interactive/static map rendering through natural language.4,861 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to access Google Maps services including places search, details, directions, geocoding, and nearby search through natural language.636 PyPI2MIT
TDQS
Scored across 36 tools
There is meaningful overlap among bbox/area retrieval tools (get_osm_elements_in_area, inspect_map_context, search_osm_elements, export_osm_data, get_osm_statistics) and among place-search/geocode tools (search_nearby_places, find_nearby_amenities, smart_geocode, resolve_location, get_place_info). Several descriptions explicitly label compatibility aliases or preferred alternatives, which helps, but selection boundaries remain fuzzy in multiple places.
Nearly all tools use snake_case and start with a verb (get_osm_node, preview_node_create, apply_osm_edit, verify_osm_edit). Minor deviations such as smart_geocode and inconsistent compound ordering (preview_poi_polygon_create vs preview_node_create) keep it from perfect consistency.
At 36 tools, the surface is heavy for the domain and includes several compatibility aliases and overlapping search/geocode helpers. The complex edit-safety workflow justifies some breadth, but the total exceeds a well-scoped range and makes the set harder to navigate.
The server covers broad read/search/validation operations and several edit preview/apply flows, including node tag edits, node creation, polygon creation, and track-road edits. However, editing coverage is uneven: relation editing, general way/relation tag updates, deletion, and explicit changeset lifecycle operations are missing or unclear, creating dead ends for common OSM edits.