Naver Search MCP vs Kagimcp — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Naver Search MCP vs Kagimcp
In-depth architectural comparison of the Naver Search MCP and Kagimcp MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Naver Search MCP
Search & Data Extraction · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Kagimcp
Search & Data Extraction · Local stdio
Quality: 82/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Naver Search MCP if you need specialized Search & Data Extraction tools running via a local process. Choose Kagimcp if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Naver Search MCP when:
You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: NCP_APIGW_API_KEY_ID, NCP_APIGW_API_KEY, NAVER_CLIENT_ID, NAVER_CLIENT_SECRET.
MCP server for Naver Search API integration, supporting blog, news, shopping search and DataLab analytics features.
The Official Model Context Protocol (MCP) server for Kagi Search & other tools.
Category & Scope
Tools & Capabilities Breakdown
Naver Search MCP Tools (18)
find_category
Category search tool so you no longer need to manually check category numbers in URLs for trend and shopping insight searches. Just describe the category in natural language.
search_webkr
Search Naver web documents
search_news
Search Naver news
search_blog
Search Naver blogs
search_cafearticle
Search Naver cafe articles
search_image
Search Naver images
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Naver Search MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Kagimcp belongs to Search & Data Extraction using local stdio subprocess. Select Naver Search MCP when you need capabilities focused on search & data extraction and Kagimcp when you require tools for search & data extraction.
Fetch web results for a query using the Kagi Search API. Use for general search and when the user explicitly tells you to 'fetch' results/information. Results are numbered so that a user may refer to a result by a specific number.
kagi_extract
Extract the content of a web page as markdown using the Kagi Extract API. Use this to read the full content of a page when needed.