get-geoLABSCO SUMMARY
Two calls, and the order matters.
get-direction expects coordinates at both ends, so the working shape is geocode first, then route — a model that skips the first step gets nothing useful. Guidance comes back as Korean turn-by-turn text, which is right for reading aloud or summarising and wrong for drawing a line on a map.
What it is
A small TypeScript server over two Naver Map APIs: one that turns a structured address into coordinates, and one that returns driving guidance between a start and a goal.
What you get
- Coordinates for a Korean structured address —
get-geo - Turn-by-turn driving guidance between a start and a goal coordinate pair —
get-direction
Requirements
Naver Map API credentials — NAVER_MAP_CLIENT_ID and NAVER_MAP_CLIENT_SECRET — plus NAVER_MAP_GEO_API_URL and NAVER_MAP_DIRECTION_API_URL for the two endpoints. Node.js 18.x or higher. Build with npm run build and point the client at dist/server.js. Directions take coordinates, so an address has to be geocoded first. Public-transport routing and lookup by place name are listed as future features, not current ones.
Setup effort
Build from source — git clone https://github.com/inchori/naver-map-direction-mcp.git
USE CASES
01
Turning an address into coordinates
Resolve a structured Korean address before doing anything that needs a latitude and longitude.
02
Routing between two addresses
Geocode both ends first, then ask for the driving guidance between the resulting points.
03
Summarising a drive for someone else
Take the turn-by-turn text and condense it into the few instructions that matter.
2 tools
Listed in project docs. Your client may show a different list.
get-directionBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- Node.js 18 or later
- NAVER_MAP_CLIENT_ID in your environment
- NAVER_MAP_CLIENT_SECRET in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/inchori/naver-map-direction-mcp.git
cd naver-map-direction-mcp
npm install
npm run buildMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"naver-map-direction-mcp": {
"command": "node",
"args": [
"<YOUR_PROJECT_PATH>/naver-map-direction-mcp/dist/server.js"
],
"env": {
"NAVER_MAP_DIRECTION_API_URL": "https://maps.apigw.ntruss.com/map-direction/v1",
"NAVER_MAP_GEO_API_URL": "https://maps.apigw.ntruss.com/map-geocode/v2",
"NAVER_MAP_CLIENT_ID": "<YOUR_NAVER_MAP_CLIENT_ID>",
"NAVER_MAP_CLIENT_SECRET": "<YOUR_NAVER_MAP_CLIENT_SECRET>"
}
}
}
}The two API URLs are NAVER Cloud Platform's Maps base addresses — the server adds /geocode and /driving itself. NAVER_MAP_CLIENT_ID and NAVER_MAP_CLIENT_SECRET are the API Key ID and API Key of your Maps application in NAVER Cloud Platform. <YOUR_PROJECT_PATH> is the folder that holds your clone.
