Naver Maps MCP Server

Created By
devyhana year ago
Model Context Protocol (MCP) 서버를 이용한 네이버 지도 API 구현
Overview

What is Naver Maps MCP Server?

Naver Maps MCP Server is a server that provides access to the Naver Maps API through the Model Context Protocol (MCP), enabling AI applications to utilize various mapping features.

How to use Naver Maps MCP Server?

To use the server, clone the repository, install dependencies, set up environment variables with your Naver API credentials, and run the server. You can also test it using MCP Inspector.

Key features of Naver Maps MCP Server?

  • Geocoding: Convert addresses to coordinates.
  • Reverse Geocoding: Convert coordinates to addresses.
  • Place Search: Search for places using keywords.
  • Route Search: Find optimal routes between two points.
  • Route Search with Waypoints: Include waypoints in route searches.
  • Coordinate System Conversion: Convert between different coordinate systems.

Use cases of Naver Maps MCP Server?

  1. Integrating mapping features into AI applications.
  2. Providing location-based services in mobile apps.
  3. Enhancing logistics and delivery services with route optimization.

FAQ from Naver Maps MCP Server?

  • What are the prerequisites for using the server?

You need Node.js 18.0.0 or higher and Naver Cloud Platform API credentials.

  • Is there a testing tool available?

Yes, you can test the server using MCP Inspector.

  • Can I use this server with other applications?

Yes, it can be integrated with applications like Claude Desktop.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
devyhan
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago