Kakao Mobility & Kakao Map MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Kakao Mobility & Kakao Map MCP Server?

This project provides a server that integrates with Kakao Mobility and Kakao Map APIs, compliant with the Model Context Protocol (MCP), aimed at offering navigation services suitable for the domestic environment.

How to use Kakao Mobility & Kakao Map MCP Server?

  1. Log in to Kakao Developers.
  2. Create an application by entering the required information and saving it.
  3. Activate the Kakao Map API in the sidebar.
  4. Obtain the REST API Key from the app settings for use.

Key features of Kakao Mobility & Kakao Map MCP Server?

  • Geocoding: Converts addresses or place names into coordinates (latitude/longitude).
  • Route search: Finds the optimal route from the starting point to the destination, supporting various modes of transportation and reflecting real-time traffic information.

Use cases of Kakao Mobility & Kakao Map MCP Server?

  1. Searching for locations using addresses or place names.
  2. Providing navigation routes for walking, driving, etc.
  3. Integrating with applications that require location-based services.

FAQ from Kakao Mobility & Kakao Map MCP Server?

  • What is the purpose of this server?

The server aims to provide efficient navigation services tailored to the local environment.

  • Is there a cost to use the Kakao Map API?

The Kakao Map API is free to use, but you must comply with Kakao's usage policies.

  • What programming language is used for this server?

The server is developed using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT 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