Naver Search MCP

Naver Search MCP

Use this skill for Korean search tasks that are better served by Naver than general web search: news, blogs, cafe posts, images, Knowledge iN, encyclopedia, local places, and DataLab trend analysis (search trends and shopping insight).

한국 웹 검색, 네이버 뉴스/블로그/카페/이미지/지식iN/백과사전/지역 검색, 네이버 DataLab 검색어 트렌드와 쇼핑인사이트 분석에 사용합니다.

github: https://github.com/isnow890/naver-search-mcp

This skill wraps the published MCP server:

npx -y @isnow890/naver-search-mcp

Setup

• Install from ClawHub with openclaw skills install naver-search-mcp.
• Supply one credential pair — never a partial mix of the two:
  • NAVER API HUB (forward path, recommended): NCP_APIGW_API_KEY_ID and NCP_APIGW_API_KEY.
  • Naver Developers (legacy, existing keys only): NAVER_CLIENT_ID and NAVER_CLIENT_SECRET. Developers Center stops accepting new applications on 2026-07-31; existing keys keep working until 2027-06-30.
• In OpenClaw, apiKey maps to NAVER_CLIENT_SECRET because this skill declares primaryEnv: NAVER_CLIENT_SECRET (kept for backward compatibility with existing legacy installs). HUB users should set both NCP_APIGW_API_KEY_ID and NCP_APIGW_API_KEY as explicit environment variables instead of using apiKey, since apiKey only ever maps to the legacy secret.
• Provide the other variable in the pair through the skill env config or OpenClaw environment (legacy users: NAVER_CLIENT_ID).
• Restart OpenClaw or the Gateway after changing credentials.
• Do not ask users to clone this repository for normal use; cloning is only for development.

Example OpenClaw config (Naver Developers, legacy, using apiKey):

{
  "skills": {
    "entries": {
      "naver-search-mcp": {
        "enabled": true,
        "apiKey": "your_naver_client_secret",
        "env": {
          "NAVER_CLIENT_ID": "your_naver_client_id"
        }
      }
    }
  }
}

Example OpenClaw config (NAVER API HUB — set both variables explicitly, do not use apiKey):

{
  "skills": {
    "entries": {
      "naver-search-mcp": {
        "enabled": true,
        "env": {
          "NCP_APIGW_API_KEY_ID": "your_ncp_apigw_api_key_id",
          "NCP_APIGW_API_KEY": "your_ncp_apigw_api_key"
        }
      }
    }
  }
}

Search Guidance

• Prefer this skill when the user wants Korean-source results, Naver-specific results, Korean shopping insight data, or Korean local data.
• Choose the tool that matches intent: news, blog reviews, cafe discussions, images, local places, encyclopedia lookup, or general Korean web search.
• search_shop, search_book, and search_academic were removed in 1.0.49 ahead of Naver's 2026-07-31 shutdown of those search APIs — do not call them. For shopping data, use DataLab Shopping Insight (datalab_shopping_* plus find_category) instead; it is a separate API and is unaffected.
• Summarize results instead of dumping raw API output. Include source, date, link, price, location, or category details when useful.

DataLab Guidance

• Use datalab_search for keyword trend comparisons.
• For shopping insight requests, call find_category first when the user gives a natural-language category such as 화장품, 노트북, or 여성의류.
• find_category is the main advantage of this MCP: users should not have to inspect Naver Shopping or DataLab URLs manually to find category codes.
• After selecting a category code, use the matching shopping trend tool for overall, device, gender, age, or keyword analysis.
• Ask the user only when multiple category candidates are genuinely ambiguous.
• For relative dates like today, recent, or current, use "today" when supported or state the assumed date range clearly.