Skip to main content
Glama
UncleSamsun

naver-mail-organizer-mcp

by UncleSamsun

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.

Related MCP server: Naver Mail MCP Server

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.

  2. Store the password locally. This command prompts for it; never put the value in the command or any configuration file.

    npx naver-mail-organizer-mcp setup --account <naver-email>
  3. Run the read-only connection check.

    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:

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>

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

npm ci
npm test
npm run pack:check

See CONTRIBUTING.md and SECURITY.md before opening an issue or pull request.

Related MCP Connectors

Related MCP Servers

  • F
    license
    A
    quality
    D
    maintenance
    A lightweight MCP server for interacting with IMAP email accounts to read messages, manage folders, and compose draft replies. It supports standard providers and local bridges, providing tools for searching, fetching attachments, and organizing mailboxes without the ability to send or delete emails.
    19
    8
    -
  • F
    license
    B
    quality
    D
    maintenance
    An MCP server that enables users to interact with their Naver Mail account via the Model Context Protocol. It allows for seamless mail integration and management within MCP-compatible clients like Claude Desktop.
    16
    -
  • A
    license
    A
    quality
    D
    maintenance
    Local MCP server for multi-account IMAP/SMTP email (iCloud + Gmail via app-specific passwords). Never marks mail read. Cross-folder search, idempotent sends, TLS verified.
    8
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables secure mailbox access and email management via IMAP/SMTP, with tools for reading, searching, organizing, sending, and deleting emails, designed for local use and compatible with MCP clients like ChatGPT.
    MIT