naver-search

This MCP server integrates with Naver's Search APIs and DataLab APIs to provide a unified interface for web, news, blogs, cafe articles, shopping, images, knowledge, encyclopedia, academic, and local searches, along with DataLab trends analysis. Once running, you can access the various tools grouped under Search Tools, DataLab Tools, and the new category search feature. Use the naver-search MCP to perform cross-service queries, fetch trend insights, and analyze shopping or term popularity through DataLab endpoints. The server supports daily keyword trend analysis and shopping insights, enabling you to compose complex queries that combine multiple Naver services in a single request.

Prerequisites:

• Node.js 18 or higher
• NPM 8 or higher
• Naver Developers API Key (Client ID and Client Secret)

Method 1: NPX Installation (Recommended)

1. Ensure Node.js and npm are installed.

2. Run the MCP directly via NPX:

   npx -y @isnow890/naver-search-mcp

3. When prompted, provide NAVER_CLIENT_ID and NAVER_CLIENT_SECRET as environment variables either in your shell or via your MCP launcher configuration.

Method 2: Local Installation (build from source)

1. Clone the repository and install dependencies:

   git clone https://github.com/isnow890/naver-search-mcp.git cd naver-search-mcp npm install npm run build

2. Start the server using Node (ensure dist/src/index.js exists after build):

   node dist/src/index.js

3. Set environment variables for NAVER_CLIENT_ID and NAVER_CLIENT_SECRET in your environment or in a startup script.

Prerequisites notes:

• After building locally, make sure the dist folder contains the compiled JavaScript files and that you point to dist/src/index.js when configuring the MCP server in your environment.
• If using Claude Desktop or other MCP managers, configure the command and args accordingly (see examples in the repository README).

Tips and common issues:

• Always provide NAVER_CLIENT_ID and NAVER_CLIENT_SECRET as environment variables when configuring the MCP to access Naver APIs.
• If you upgrade the MCP package, re-run npm install and, for local builds, npm run build to regenerate dist.
• The NPX approach fetches the latest release, which helps stay up-to-date with features like the new 'today' keyword in DataLab, but may require network access at runtime.
• For debugging, check logs for API key errors or rate limiting from Naver APIs; ensure your Naver Developers account has the required API permissions enabled (Search, DataLab - Search Trends, and DataLab - Shopping Insight).
• When using Claude or other clients, ensure the config paths (cwd, command, and argument list) point to the correct installed location and that the dist path is accurate.