# Naver Mail Organizer MCP

Local-only MCP tools for reviewing and organizing a Naver Mail account through
IMAP. This is an independent project and is not affiliated with, endorsed by, or supported by NAVER.

## Safety first

The connector stores its application password in the local OS credential store
and fixes IMAP to `imap.naver.com` over TLS port `993`. Never share an
application password, verification code, message body, attachment, audit record,
or other secret in chat, Git, issues, client configuration, or `.env` files.

Mail moves require an approved, unexpired review plan. Automatic spam moves are
**off by default**. They may be enabled only in generated or manually edited MCP client configuration by setting `NAVER_MAIL_ALLOW_AUTO_SPAM=true`; only literal `true` enables automatic spam moves. There is no command-line spam opt-in.

## Quick start

1. In Naver Mail on a PC, enable IMAP/SMTP at
   `환경설정 > POP3/IMAP 설정 > IMAP/SMTP 설정`, then create a dedicated application
   password after enabling two-step verification. Naver documents the setup and
   revoke path in its [IMAP/SMTP help](https://help.naver.com/service/30029/contents/21344?osType=COMMONOS).
2. Store the password locally. This command prompts for it; never put the value
   in the command or any configuration file.

   ```sh
   npx naver-mail-organizer-mcp setup --account <naver-email>
   ```

3. Run the read-only connection check.

   ```sh
   npx naver-mail-organizer-mcp doctor --account <naver-email>
   ```

4. Generate the configuration for your MCP client and install it using that
   client's normal configuration flow. Do not change generated entries to add
   secrets.

## Client configuration

Generate a configuration for the account you stored locally:

```sh
npx naver-mail-organizer-mcp config codex --account <naver-email>
npx naver-mail-organizer-mcp config claude --account <naver-email>
npx naver-mail-organizer-mcp config claude-desktop --account <naver-email>
```

- **Codex:** paste the generated TOML into the MCP configuration location shown
  by Codex. See the [Codex registration guide](https://github.com/UncleSamsun/naver-mail-organizer-mcp/blob/main/docs/codex-mcp-registration.md)
  and the [Codex MCP documentation](https://developers.openai.com/codex/mcp/).
- **Claude Code:** run the generated `claude mcp add` command in your terminal,
  then verify it in Claude Code's MCP settings; see the [Claude Code MCP
  guide](https://code.claude.com/docs/en/mcp).
- **Claude Desktop:** merge the generated JSON server entry into Claude
  Desktop's MCP configuration file, then restart Claude Desktop. See
  [Anthropic's local MCP setup guide](https://support.claude.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop).

To explicitly allow automatic spam moves, regenerate the specific client entry
with `--allow-auto-spam`, then install that generated configuration. It adds only
`NAVER_MAIL_ALLOW_AUTO_SPAM=true` to the client environment; only literal `true`
enables the behavior. Remove that environment setting to return to the safe
default. Do not add a spam option to a server command.

## Revoking access

Disable IMAP/SMTP at the Naver settings path above or delete the dedicated
application password in Naver ID security settings. Delete local credentials
through your OS credential manager if necessary.

## Development

```sh
npm ci
npm test
npm run pack:check
```

See [CONTRIBUTING.md](https://github.com/UncleSamsun/naver-mail-organizer-mcp/blob/main/CONTRIBUTING.md) and [SECURITY.md](SECURITY.md) before
opening an issue or pull request.