Mcp Server Kakao Map

Created By
cgoinglovea year ago
kakao map mcp server
Overview

what is Mcp Server Kakao Map?

Mcp Server Kakao Map is a server application that utilizes the Kakao Map API to provide location-based place recommendations within South Korea, optimized for Korean language queries.

how to use Mcp Server Kakao Map?

To use the Mcp Server Kakao Map, you need to set up your environment with a valid Kakao API key and make queries using Korean keywords to receive recommendations for places like restaurants, shops, and attractions.

key features of Mcp Server Kakao Map?

  • Provides recommendations for various places based on user queries.
  • Utilizes the Kakao Map API for accurate location-based results.
  • Supports Korean language queries for better user experience.

use cases of Mcp Server Kakao Map?

  1. Finding popular restaurants in Itaewon.
  2. Locating hospitals in Seoul.
  3. Discovering cafes near Gangnam Station.

FAQ from Mcp Server Kakao Map?

  • What kind of places can I find using this service?

You can find restaurants, shops, public facilities, and attractions in South Korea.

  • Do I need an API key to use this service?

Yes, you need to register an application with Kakao Developers and obtain a REST API key.

  • Is this service available in languages other than Korean?

Currently, the service is optimized for Korean language queries.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cgoinglove
Star
1
Language
TypeScript
License
MIT license

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago