mcp-server-naver-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAVER_CLIENT_ID | Yes | Your Naver Developers API Client ID. | |
| NAVER_CLIENT_SECRET | Yes | Your Naver Developers API Client Secret. |
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_naverA | |
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 1 tool
Only one tool exists, so there is no ambiguity in tool selection. The single tool's purpose is clear and distinct.
The single tool follows a consistent verb_noun pattern ('search_naver'), which is clear and predictable.
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.
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.