Skip to main content
Glama
uju777

mcp-server-naver-search

by uju777

Naver Search MCP Server

Connecting Claude Desktop & Cursor to Naver(Korea's #1 Search Engine). Claude에서 네이버 쇼핑 최저가, 카페 리얼 후기, 실시간 뉴스를 검색하세요.

Why use this? Brave Search or Google often fail to retrieve local Korean information (Prices, Cafe posts, News). This MCP serves as a bridge to Naver's robust database.

Key Features

  • Shopping (쇼핑): Compare lowest prices from Naver Shopping.

  • Cafe (카페): Search community posts (Naver Cafe) for real user reviews.

  • News (뉴스): Get real-time Korean news articles.

  • Blog (블로그): Find authentic reviews from Korean bloggers.

Related MCP server: naver-mcp

Quick Start

1. Prerequisites

2. Installation

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "naver-search": {
      "command": "uv",
      "args": [
        "run",
        "--with", "mcp[cli]",
        "--with", "httpx",
        "--with", "python-dotenv",
        "/YOUR/PATH/TO/mcp-server-naver-search/server.py"
      ],
      "env": {
        "NAVER_CLIENT_ID": "YOUR_ID",
        "NAVER_CLIENT_SECRET": "YOUR_SECRET"
      }
    }
  }
}

Add this to your ~/.claude/settings.json:

{
  "mcpServers": {
    "naver-search": {
      "command": "sh",
      "args": [
        "-c",
        "export PATH=\"$HOME/.local/bin:$PATH\" && cd /YOUR/PATH/TO/mcp-server-naver-search && uv run --with 'mcp[cli]' --with httpx --with python-dotenv python server.py"
      ],
      "env": {
        "NAVER_CLIENT_ID": "YOUR_ID",
        "NAVER_CLIENT_SECRET": "YOUR_SECRET"
      }
    }
  }
}

Note: Claude Code requires sh -c with PATH export because it doesn't inherit your shell's PATH configuration.

Add this to your Cursor MCP settings:

{
  "mcpServers": {
    "naver-search": {
      "command": "uv",
      "args": [
        "run",
        "--with", "mcp[cli]",
        "--with", "httpx",
        "--with", "python-dotenv",
        "/YOUR/PATH/TO/mcp-server-naver-search/server.py"
      ],
      "env": {
        "NAVER_CLIENT_ID": "YOUR_ID",
        "NAVER_CLIENT_SECRET": "YOUR_SECRET"
      }
    }
  }
}

Usage Examples (Try these!)

After restarting Claude, ask:

1. Shopping - Find Lowest Price

"맥북 프로 M4 14인치 네이버 쇼핑 최저가 알려줘. 판매처랑 가격 비교해줘."
("Find the lowest price for MacBook Pro M4 on Naver Shopping.")

2. Cafe - Real Community Reviews

"서울 성수동 데이트 코스 추천해줘. 네이버 카페 글 위주로 찾아줘."
("Recommend date spots in Seongsu-dong using Naver Cafe posts.")

3. News - Breaking News

"오늘 삼성전자 주가 관련 뉴스 5개만 요약해줘."
("Summarize 5 latest news articles about Samsung Electronics stock.")

License

MIT License © 2026 uju777

This project is licensed under the MIT License - see the LICENSE file for details.


Contributing

Issues and Pull Requests are welcome!

Author

uju777 - GitHub

Available Tools

1 tool
search_naverA
네이버 검색 API를 사용하여 한국 현지 정보를 검색합니다.

Args:
    query (str): 검색어 (예: "맥북프로 M4 최저가", "삼성전자 주가 뉴스")
    category (str): 검색 카테고리
        - "shop": 쇼핑 최저가 검색 (★인기 기능)
        - "cafe": 네이버 카페 글 검색 (★찐 후기)
        - "news": 실시간 뉴스 기사
        - "blog": 블로그 리뷰
        - "local": 맛집, 장소 전화번호
    display (int): 가져올 결과 개수 (기본 5개)
ParametersJSON Schema
NameRequiredDescriptionDefault
queryYes
categoryNoblog
displayNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It correctly implies a read-only search operation but does not explicitly state that it is non-destructive, mention authentication requirements, or describe rate limits. These omissions are minor for a straightforward search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear opening sentence and a labeled 'Args' section. While slightly verbose with emojis and examples, every sentence adds value. It is front-loaded with the core purpose. Could be more concise by removing redundant phrasing, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (3 parameters, output schema present), the description provides adequate context. It covers all parameters and use cases. The presence of an output schema alleviates the need to explain return values. Missing details like error handling or pagination are not critical for this simple search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, so the description entirely compensates by providing detailed parameter semantics. It explains the 'query' parameter with an example, lists all 'category' options with emojis and usage tips (e.g., '★인기 기능'), and specifies the default for 'display'. This adds significant meaning beyond the schema's type definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it searches Naver API for Korean local information, with a specific verb ('search') and resource ('Naver search API'). It lists five distinct categories (shop, cafe, news, blog, local), making the purpose unambiguous even without sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit context for when to use the tool (for searching Korean local information via Naver). It details each category with practical examples, helping the agent choose appropriately. However, it does not provide exclusions or mention alternatives since no sibling tools exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

TDQS

A4.4/5.0
Disambiguation5/5

Only one tool exists, so there is no ambiguity in tool selection. The single tool's purpose is clear and distinct.

Naming Consistency5/5

The single tool follows a consistent verb_noun pattern ('search_naver'), which is clear and predictable.

Tool Count4/5

While only one tool exists, it effectively encapsulates all search functionality (shop, cafe, news, blog, local) via a category parameter, making it well-scoped for a focused search server.

Completeness5/5

The tool covers all major Naver search categories (shop, cafe, news, blog, local) and allows customization of result count, providing a complete surface for searching Korean local information.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    Provides access to Naver Search APIs, allowing AI agents to search across multiple categories (blogs, news, books, images, shopping items, etc.) with structured responses optimized for LLM consumption.
    13
    4
    Apache 2.0
  • F
    license
    A
    quality
    C
    maintenance
    Naver Search API + Datalab API MCP server with 19 tools for Korean web search and trend analysis.
    19
    19
  • A
    license
    B
    quality
    D
    maintenance
    Provides tools to search Naver services (web, news, blog, etc.) and analyze search trends using Naver DataLab, with all required MCP protocol methods implemented for compatibility with Cursor and Claude Desktop.
    20
    34
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    MCP server for Naver Search Open API, enabling search news, blog, and shop functionalities through natural language.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/uju777/mcp-server-naver-search'

If you have feedback or need assistance with the MCP directory API, please join our Discord server