INAVI Maps API MCP Server
OfficialRelated Servers
Alternatives to INAVI Maps API 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.813 npm7Apache 2.0
Neshan MCP Serverofficial
FlicenseAqualityCmaintenanceEnables AI assistants to access Neshan maps services for location search, routing, traffic analysis, and more through natural language.166-- AlicenseAqualityDmaintenanceIntegrates Korean APIs (Naver, Kakao, TMAP) into LLM applications for search, maps, and directions.111MIT
- AlicenseNot gradedqualityCmaintenanceEnables location-aware AI agents to search for nearby places, get detailed place information including hours and ratings, and calculate routes with turn-by-turn directions using Google Maps APIs.22MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.1,553 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to access Google Maps services including places search, details, directions, geocoding, and nearby search through natural language.62MIT
TDQS
Scored across 12 tools
Every tool has a clearly distinct purpose, and descriptions explicitly include ALTERNATIVES sections that route agents to the correct sibling tool (e.g. search_places vs search_nearby_category, find_route vs find_walking_route vs get_distance_matrix vs optimize_waypoint_order). The geocode/reverse_geocode pair is cleanly separated by direction. This is close to ideal disambiguation.
All names are snake_case verb_noun constructions, largely consistent (search_places, find_route, get_admin_boundary). Minor inconsistency in verb choice — search/find/lookup/get/geocode/reverse coexist — which is readable but not a single uniform pattern.
Twelve tools sit comfortably in the well-scoped range, and each maps to a distinct capability (search, geocode, route, matrix, optimize, boundary, entry points). The one internal tool, get_map_config, is justified for the map template.
The surface covers search, forward/reverse geocoding, driving and walking routing, distance matrix, waypoint ordering, category lookup, and admin boundaries — a strong lifecycle. Minor gaps: no place-details lookup by ID and no public-transit routing, but these are workaroundable.