Give your AI agent a real 126.com mailbox. Read, search, send, reply, schedule and organize mail over IMAP with a NetEase authorization code issued for that mailbox, not for a sibling one.
Claude cannot reach a NetEase 126 mailbox on its own. mcpemails is a hosted MCP server that connects it over IMAP at imap.126.com on port 993, authenticating with the 16-character client authorization code (客户端授权码) NetEase issues for that mailbox rather than your password. Almost every English guide to NetEase mail is written for 163.com, and pointing a 126 address at the 163 hostnames fails as an authentication error rather than as a routing one, which sends people back to regenerating a code that was never wrong. One inbox is free.
126.com is NetEase's second free mail domain, opened after the 163.com namespace filled up, and it is where a large share of Chinese personal addresses actually live. It runs on the same Coremail platform as 163.com and behaves the same way, but it is a different mailbox on different servers: IMAP at imap.126.com on port 993 over TLS, and SMTP at smtp.126.com on port 465. Two conditions have to hold before a client logs in. The client protocol must be switched on in the mailbox settings, which is what produces the 16-character authorization code that replaces your password. And the client has to identify itself with the IMAP ID command before it authenticates, because NetEase refuses anonymous clients with an Unsafe Login message that has nothing to do with credentials. mcpemails does both.
Copy these into the connect form. mcpemails prefills them where it can, and retries the other standard transport if the first does not answer.
| Protocol | Server | Port | Security |
|---|---|---|---|
| IMAP (incoming) | imap.126.com | 993 | TLS (implicit) |
| SMTP (outgoing) | smtp.126.com | 465 | TLS (implicit) |
Verified 2026-08-31: imap.126.com answered a TLS connection and identified itself as an IMAP server under that name. It advertises XOAUTH2 authentication.
Sign in with: Your full address, including the domain: name@126.com.
Nine action-based MCP tools: send, reply, forward, schedule, and organize. Your agent finishes the job inside NetEase 126.
List, read and search across folders to find that invoice, summarize a thread, or pull the latest from a sender.
Compose and send real messages, reply in-thread, and forward, directly from your mailbox, not as a draft you finish by hand.
Queue a message to go out at the right time, so your agent can draft now and send on schedule.
Keep the inbox tidy: file mail into folders, flag what matters, archive the rest, or delete on request.
From sign-up to first AI email in a couple of minutes.
Sign up at mcpemails.com. The free plan connects one inbox and stays free, with no card required. Keep your phone to hand: NetEase asks you to send a verification SMS partway through the next step.
Sign in at mail.126.com, not at mail.163.com, even if you hold both. Open 设置 (Settings) and choose POP3/SMTP/IMAP. Switch the IMAP/SMTP service on and confirm in the popup. NetEase will offer its own 邮箱大师 client first; carry on past it. Until this service is on, imap.126.com refuses every login whatever password you send.
NetEase shows a QR code that composes a verification SMS on your phone, with a manual-send fallback underneath it. Send the message, wait a moment, then confirm you have sent it. The 16-character authorization code appears once and is never shown again. Copy it, choose IMAP / SMTP in mcpemails, enter your full 126 address, and paste the code into the password field. The 126 hosts are prefilled.
Drop https://mcpemails.com/api/mcp into Claude, Cursor or ChatGPT, authorize, and your agent can read, search, send, reply, forward, schedule and organize that 126 mailbox.
Comparing providers first? See the email provider compatibility matrix
This is the one that costs 126 users the most time, and it is a side effect of documentation rather than of the service. The overwhelming majority of guides, sample configurations and Stack Overflow answers about NetEase mail were written for 163.com, so imap.163.com and smtp.163.com are what people copy. A name@126.com address presented to the 163 server is simply an account that does not exist there, and the server reports that as a failed login. Nothing in the message says you are at the wrong host. Before you regenerate a code, check that the hostnames actually say 126.
NetEase runs 126.com alongside 163.com, yeah.net and 188.com, and lets you associate them so that several mailboxes are reachable from a single sign-in. That convenience makes people assume the credential is shared too. It is not. Each mailbox has its own client protocol switch, its own authorization code and its own hostnames, and a code minted for your 163 address authenticates nothing at imap.126.com. If you hold both, connect them in mcpemails as two separate inboxes with two separate codes.
First, NetEase requires third-party clients to announce themselves with the IMAP ID command from RFC 2971 before authenticating. A client that skips it is refused with Unsafe Login, and NetEase drops a warning message into the mailbox as well. The referral address in that message is at yet another NetEase domain, which adds to the confusion. Second, the server's capability line advertises AUTH=XOAUTH2 and nothing else, so a client picking a mechanism from the advertised list finds none it can use with a password and never attempts the plain LOGIN command that does work. Both look exactly like a bad authorization code. mcpemails handles both.
Not directly. Claude has no built-in NetEase connector and cannot open an IMAP connection by itself. Connecting an MCP server such as mcpemails to your 126 mailbox gives Claude read, search, send, reply, forward, schedule and organize access to it, and the same connection works from Cursor and other MCP clients.
IMAP is imap.126.com on port 993 with implicit TLS. SMTP is smtp.126.com on port 465. Log in with your full 126.com address and the 16-character client authorization code rather than your mailbox password. Both hosts were verified from a live TLS connection on the date shown on this page.
No. They are separate mailboxes on separate hostnames, even when both are reachable from one NetEase sign-in. Each one issues its own code from its own settings screen, and each one has its own client protocol switch that has to be turned on. Generate a code at mail.126.com for the 126 address.
Sign in at mail.126.com, open 设置 then POP3/SMTP/IMAP, and switch the IMAP and SMTP service on. NetEase then asks you to send a verification SMS from the phone bound to the account. Once that is confirmed, the 16-character code is displayed a single time, so copy it before closing the dialog.
It is the same company and the same Coremail platform, with the same authorization code flow and the same IMAP identification requirement, but it is a different mail domain with its own servers. Treat it as a separate provider when you configure a client, and read the hostnames carefully, because they differ by three characters.
No. Messages are fetched live from NetEase over IMAP for each request and passed to your AI client. Credentials are encrypted at rest, and message bodies are not retained after the request that asked for them.
Connect your 126.com mailbox in minutes with its own authorization code. One inbox free forever, no card required.