MCP Naver Maps
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAVER_CLIENT_API | Yes | Your Naver Developers API Client ID | |
| NAVER_CLIENT_SECRET | Yes | Your Naver Developers API Client Secret | |
| NAVER_MAPS_CLIENT_ID | Yes | Your Naver Maps API Client ID from Naver Cloud Platform | |
| NAVER_MAPS_CLIENT_SECRET | Yes | Your Naver Maps API Client Secret from Naver Cloud Platform |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocodeB | Searches for address information related to the entered address. |
| localSearchC | Searches for places registered with Naver's local service. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.