KiMCP (Korea-integrated Model Context Protocol)

Created By
zeikara year ago
MCP server enabling LLMs to use Korean APIs (Naver, Kakao, etc.)
Overview

What is KiMCP?

KiMCP (Korea-integrated Model Context Protocol) is a server implementation of the Model Context Protocol (MCP) that integrates various Korean APIs into large language model (LLM) applications.

How to use KiMCP?

To use KiMCP, clone the repository from GitHub, install the necessary dependencies, configure your Naver API credentials, and run the MCP server on Claude Desktop.

Key features of KiMCP?

  • Naver Blog Search: Retrieve blog content from Naver.
  • Naver News Search: Access news articles from Naver.
  • Naver Cafe Search: Find articles from Naver Cafe communities.
  • Naver Knowledge iN Search: Search Q&A articles from Naver Knowledge iN.
  • Naver Local Search: Get information about local businesses and places.
  • Naver Image Search: Search for images on Naver.
  • Naver Shopping Search: Find products and compare prices on Naver Shopping.

Use cases of KiMCP?

  1. Integrating Korean content into AI applications.
  2. Enhancing LLMs with localized search capabilities.
  3. Developing applications that require access to Naver's extensive data.

FAQ from KiMCP?

  • What are the prerequisites for using KiMCP?

You need Claude Desktop, the uv Python Package Manager, and Naver API credentials.

  • Is KiMCP free to use?

Yes, KiMCP is open-source and free to use under the MIT License.

  • What is the roadmap for KiMCP?

Future integrations include Kakao API and Korea Meteorological Administration (KMA) integration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zeikar
Star
3
Language
Python
License
MIT license

Recommend Servers

View All
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.

7 hours ago
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