SuperAPI AI Directory

naver-search-mcp

Naver Search API integration: blog, news and shopping search plus DataLab analytics.

Open website

About this tool

Naver Search MCP Server is a Model Context Protocol (MCP)-based server for integrating the Naver Search API and DataLab API into MCP-enabled clients. It provides comprehensive search capabilities across Naver services, as well as data trend analysis tools via the DataLab API.

Purpose

The main purpose of this server is to enable AI clients (such as Claude Desktop, Cursor, Claude Code, Cline, etc.) to directly call Naver's search and data analysis features. Users can retrieve web pages, news, blogs, and other content on Naver through natural language or tool calls in these clients, and analyze search term and shopping trends.

Main Capabilities

The server provides the following tool categories:

Category Lookup

  • find_category: Without needing to know the category number, search for the category ID required for shopping insights via natural language.

Search Tools

  • search_webkr: Web document search
  • search_news: News search
  • search_blog: Blog search
  • search_cafearticle: Cafe article search
  • search_image: Image search
  • search_kin: Knowledge iN search
  • search_encyc: Encyclopedia search
  • search_local: Local place search

DataLab Trend Analysis

Date parameters support the "today" keyword (e.g., endDate: "today").

  • datalab_search: Search term trend analysis
  • datalab_shopping_category: Click trends by shopping category
  • datalab_shopping_by_device: Shopping trends by device (PC/mobile)
  • datalab_shopping_by_gender: Shopping trends by gender
  • datalab_shopping_by_age: Shopping trends by age group
  • datalab_shopping_keywords: Shopping keyword trends
  • datalab_shopping_keyword_by_device: Keyword trends by device- datalab_shopping_keyword_by_gender: Keyword trends by gender
  • datalab_shopping_keyword_by_age: Keyword trends by age

Usage

In the configuration file of an MCP client (such as Claude Desktop, Cursor, Claude Code, Cline, etc.), add the following settings to mcpServers.

Note: The Kakao PlayMCP integration service has ended support. Please set up and use the API key directly in a local environment.

1. NAVER API HUB (Recommended / Newly Issued)

When using a NAVER API HUB key from Naver Cloud Platform (NCP).

2. Naver Developers Center (Existing Issuers Only)

When using an existing Naver Developers Center (openapi.naver.com) key (supported until 2027-06-30).

3. OpenClaw (ClawHub)

When using OpenClaw, it can be installed immediately via the ClawHub skill.

Note: In the OpenClaw environment, you need to set either the NAVER API HUB pair (NCP_APIGW_API_KEY_ID / NCP_APIGW_API_KEY) or the Developers Center pair (NAVER_CLIENT_ID / NAVER_CLIENT_SECRET). Depending on the environment variable pair used, the calling platform is determined automatically. (Please set only one of the pairs)

Use Cases

  • Retrieve Naver web pages, news, blogs, cafe articles, images, Knowledge iN, encyclopedia, and local place information in AI clients.
  • Analyze search term trends to understand how keywords change over time.
  • Analyze shopping trends, viewing click or keyword trends by dimensions such as category, device, gender, and age.
  • Query shopping category IDs via natural language, simplifying the use of shopping insights.

Limitations

  • A Naver API key must be configured, supporting either NAVER API HUB or Naver Developers Center.
  • Naver Developers Center keys are supported until 2027-06-30.
  • The Kakao PlayMCP integration service has ended support.
  • In the OpenClaw environment, only one pair of environment variables can be set (the NAVER API HUB pair or the Developers Center pair).
  • Other feature details, fees, pricing, platform support, etc. are not yet provided.