A
licenseA
qualityB
maintenanceProvides location-based services and geospatial data from OpenStreetMap, enabling geocoding, route directions, nearby place search, and neighborhood analysis through natural language.
12
MIT
OpenStreetMap MCP Server v2
by ogSINGH
Related Servers
Alternatives to OpenStreetMap MCP Server v2
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn OpenStreetMap MCP server that provides location-based services including geocoding, route directions, points of interest search, and neighborhood analysis to enhance LLMs with geospatial capabilities.121MIT
- AlicenseAqualityBmaintenanceAn OpenStreetMap MCP server providing geocoding, routing, points of interest, map tiles, public transport, and energy infrastructure tools to enhance LLM location-based capabilities.16MIT
- FlicenseAqualityCmaintenanceOSM-backed multimodal navigation MCP server enabling geocoding, route planning, POI discovery, and urban layout analysis. It provides a structured city graph to LLM apps without proprietary map APIs.8-
Magic Lane MCP Serverofficial
AlicenseBqualityBmaintenanceEnables 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.822 npm7Apache 2.0- AlicenseAqualityDmaintenanceEnhances LLM capabilities with location-based services and geospatial data, enabling users to geocode addresses, find nearby points of interest, get directions, optimize meeting points, and analyze neighborhoods.12226MIT
TDQS
A3.6/5.0
Scored across 12 tools
Disambiguation3/5
Several tools overlap substantially: explore_area, find_nearby_places, analyze_neighborhood, and search_category all return categorized POIs in an area, and find_schools_nearby, find_ev_charging_stations, and find_parking_facilities are essentially specialized subsets that find_nearby_places could handle. The descriptions help distinguish analysis-oriented tools (analyze_neighborhood, explore_area) from search-oriented ones, but an agent could still easily misselect among the area-search family.
Naming Consistency5/5
Every tool follows a clean verb_noun pattern (explore_area, reverse_geocode, geocode_address, find_nearby_places, get_route_directions, search_category, suggest_meeting_point, analyze_commute, etc.). Verbs are consistent (find_/get_/analyze_/search_) and naming is fully snake_case with no deviations.
Tool Count4/5
12 tools is a reasonable, well-scoped size for an OSM geospatial server covering geocoding, routing, search, and analysis. It's slightly heavy given the redundant specialized search tools, but nothing feels padded to the point of being unmanageable.
Completeness4/5
Core geospatial workflows are well covered: both geocoding directions, routing, POI/category search, area and neighborhood analysis, and specialized searches. Minor gaps exist (e.g., isochrones, elevation, map/static image generation, or boundary/administrative lookups), but agents can accomplish most realistic tasks.
Maintenance
ActivityMaintained
ResponsivenessNo issues