MCP Naver Maps
Related Servers
Alternatives to MCP Naver Maps
No user-submitted related servers found.
Related Servers
- -licenseAqualityNot gradedmaintenanceEnables users to access Naver Maps API functionality including directions, place search, geocoding, and reverse geocoding through a Model Context Protocol server.4-
- AlicenseNot gradedqualityBmaintenanceUnified MCP server for place search and geocoding across Kakao, Naver, and Google Maps APIs with automatic provider fallback.MIT
- AlicenseCqualityDmaintenanceA server that connects to SK TMAP API, providing access to public transit routing and geocoding functionality through a standardized interface.2MIT
- AlicenseNot gradedqualityDmaintenanceA server that enables AI models to access Kakao Map features (place search, address lookup, route finding) and Daum search services (web, image, blog, cafe) through Model Context Protocol.17MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for Naver Search Open API, enabling search news, blog, and shop functionalities through natural language.-
- FlicenseAqualityCmaintenanceNaver Search API + Datalab API MCP server with 19 tools for Korean web search and trend analysis.1911 npm-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: geocode handles address-to-coordinate conversion, while localSearch finds registered places. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.
Both tools follow a consistent naming pattern using camelCase (geocode, localSearch) with descriptive verb-noun structures. The naming is uniform and predictable across the set.
With only two tools, the server feels under-scoped for a maps domain. While geocoding and local search are core functions, typical maps services include additional operations like routing, place details, or reverse geocoding, making this set appear incomplete.
For a maps server, there are significant gaps in coverage. Missing tools for routing, reverse geocoding, place details, or map visualization limit an agent's ability to handle common mapping workflows, leading to potential dead ends in tasks.