Naver Mail MCP Server
# Mail MCP Server
## 실행환경 설정
## MCP Server 연동
### 테스트
1. inspector 다운로드 및 실행(node가 설치되어있어야 함)
```sh
npx @modelcontextprotocol/inspector uv run server.py --naver-id your-id --naver-password your-password
```
2. Session Token 복사
```
Starting MCP inspector...
⚙️ Proxy server listening on 127.0.0.1:6277
🔑 Session token: 3518ab7ad6026be0f0ad8d5c0ef9b2c853e48ed911fe1317eb9b0ed48bdd980e <--- 이거 복사
Use this token to authenticate requests or set DANGEROUSLY_OMIT_AUTH=true to disable auth
🔗 Open inspector with token pre-filled:
http://localhost:6274/?MCP_PROXY_AUTH_TOKEN=3518ab7ad6026be0f0ad8d5c0ef9b2c853e48ed911fe1317eb9b0ed48bdd980e
🔍 MCP Inspector is up and running at http://127.0.0.1:6274 🚀
```
3. 127.0.0.1:6274 접속 및 Configuration 설정
**Configuration** -> **Proxy Session Token** 에 **2. Session Token 복사**에서 복사한 키 설정
4. Connect 실행
### Claude Desktop
1. ~/Library/Application Support/Claude/claude_desktop_config.json 파일을 엽니다.(없으면 파일을 만들어주세요.)
2. 아래 내용 중 `/ABSOLUTE/PATH/TO/naver-mail-mcp`와 `--naver-id`, `--naver-password`는 수정해주세요
```json
{
"mcpServers": {
"naver-mail": {
"command": "uv",
"args": [
"--directory",
"/ABSOLUTE/PATH/TO/naver-mail-mcp",
"run",
"server.py",
"--naver-id",
"your-id",
"--naver-password",
"your-password"
]
}
}
}
```
3. 파일 저장 후 Claude Desktop을 재시작해주세요TDQS
Scored across 16 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are well-organized around specific operations like copying vs. moving mails, different marking states, and separate listing methods. The descriptions clearly differentiate each tool's function.
All tools follow a consistent verb_noun naming pattern with clear, descriptive names. The naming convention is uniform throughout (e.g., copy_mails, create_folder, list_mails), making it easy to understand each tool's function at a glance.
With 16 tools, this is well-scoped for a mail management server. Each tool earns its place by covering essential operations like folder management, mail listing, status updates, and basic utilities without being excessive or redundant.
The toolset provides complete CRUD/lifecycle coverage for email management. It includes folder operations (create, delete, rename, list), mail operations (list, get detail, copy, move, delete), status management (read/unread, important/unimportant), and utility functions (ping, debug). No obvious gaps exist for the domain.