Mcp Kakao Local

Created By
yunkee-leea year ago
The MCP connects to the Kakao Local API (https://developers.kakao.com/docs/latest/ko/local/common).
Overview

What is MCP Kakao Local?

MCP Kakao Local is a project that connects to the Kakao Local API, allowing users to access location-based services and data from Kakao.

How to use MCP Kakao Local?

To use MCP Kakao Local, you need to set up your environment by installing Python and the required dependencies, configure your API credentials, and then run the server using the provided commands.

Key features of MCP Kakao Local?

  • Integration with Kakao Local API for location services
  • Easy setup with environment configuration
  • Ability to run a local server for development and testing

Use cases of MCP Kakao Local?

  1. Accessing local business information through Kakao.
  2. Implementing location-based services in applications.
  3. Developing applications that require mapping and geolocation features.

FAQ from MCP Kakao Local?

  • What are the prerequisites for using MCP Kakao Local?

You need Python 3.13 or higher and API credentials from Kakao Developers.

  • How do I run the MCP server?

You can run the server using the command uv run src/mcp_kakao_local after syncing dependencies.

  • Is there a way to test the application locally?

Yes! You can run the server in development mode using mcp dev src/mcp_kakao_local/server.py.

Server Config

{
  "mcpServers": {
    "mcp-kakao-local": {
      "command": "uv",
      "args": [
        "run",
        "src/mcp_kakao_local"
      ],
      "env": {
        "REST_API_KEY": "YOUR_REST_API_KEY_HERE"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yunkee-lee
Star
-
Language
-
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)

2 days ago