Naver MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAVER_CLIENT_ID | Yes | Your Naver Client ID obtained from Naver Open API | |
| NAVER_CLIENT_SECRET | Yes | Your Naver Client Secret obtained from Naver Open API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_blogC | Search blog posts on Naver |
| search_newsC | Search news articles on Naver |
| search_bookC | Search books on Naver |
| get_book_advD | Get book information from Naver |
| adult_checkC | Check if the search term is adult content |
| search_encycC | Search encyclopedia on Naver |
| search_cafe_articleC | Search cafe articles on Naver |
| search_kinC | Search Q&A on Naver |
| search_localC | Search local information on Naver |
| fix_spellingC | Correct spelling errors in a given text |
| search_webkrC | Search web pages on Naver |
| search_imageC | Search images on Naver |
| search_shopC | Search shopping items on Naver |
| search_docC | Search documents on Naver |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools are clearly separated by search domain (blog, news, book, image, shop, etc.), so an agent can usually pick the right one. Minor ambiguity exists between search_book and get_book_adv, and search_doc vs search_webkr may require interpretation.
The dominant pattern is search_<domain>, used consistently across most tools. A few utility/detail tools deviate (get_book_adv, adult_check, fix_spelling), but they remain readable and not chaotic.
14 tools is well within a reasonable range for a search-oriented MCP server. Each tool maps to a distinct Naver search category or small utility, so the count feels well-scoped.
The surface covers a broad set of Naver search domains plus adult-content checking and spelling correction. There are minor gaps such as limited detail-fetching beyond books and no obvious movie/other Naver search categories, but core search workflows are covered.