Connect Namecheap Private Email to Claude,
and Cursor, ChatGPT, any MCP client
Give your AI agent a real Namecheap Private Email inbox in minutes. Read, search, send, reply, schedule and organize mail with IMAP and your mailbox password, and use the same inbox in every MCP client, not just one.
Claude cannot reach Namecheap Private Email on its own. mcpemails is a hosted MCP server that connects it over IMAP using your mailbox password, so Claude, Cursor or any MCP client can read, search, send and organize that mail. Setup takes a couple of minutes and one inbox is free.
How Namecheap Private Email connects: IMAP and your mailbox password
Namecheap Private Email connects over IMAP/SMTP with the mailbox password, the one set when the mailbox was created rather than your Namecheap account password. Both hosts are mail.privateemail.com whatever your domain is. If you do not have the password, reset it from the Private Email control panel.
The exact Namecheap Private Email IMAP and SMTP settings
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) | mail.privateemail.com | 993 | TLS (implicit) |
| SMTP (outgoing) | mail.privateemail.com | 465 | TLS (implicit) |
Verified 2026-08-31: mail.privateemail.com answered a TLS connection and identified itself as an IMAP server under that name. It advertises LOGIN, PLAIN authentication.
Sign in with: Your full address at your own domain, for example you@yourdomain.com. Namecheap's guide gives the email address as the username.
A Namecheap Private Email inbox your agent can actually use
Nine action-based MCP tools: send, reply, forward, schedule, and organize. Your agent finishes the job inside Namecheap Private Email.
- 01Read
Read & search mail
List, read and search across folders to find that invoice, summarize a thread, or pull the latest from a sender.
- 02Send
Send, reply & forward
Compose and send real messages, reply in-thread, and forward, directly from your mailbox, not as a draft you finish by hand.
- 03Schedule
Schedule for later
Queue a message to go out at the right time, so your agent can draft now and send on schedule.
- 04Organize
Move, copy, flag, archive, delete
Keep the inbox tidy: file mail into folders, flag what matters, archive the rest, or delete on request.
Connect Namecheap Private Email in four steps
From sign-up to first AI email in a couple of minutes.
Create a free account
Sign up for mcpemails, no card required. The free plan connects one inbox, forever.
Find your Private Email mailbox password
Use the password for the mailbox itself, not your Namecheap account password. You can reset it from the Private Email control panel at any time.
Paste it into mcpemails
Choose IMAP / SMTP, add your Namecheap Private Email address, the hosts below and the password to connect the inbox securely.
Paste the MCP URL into your AI
Drop https://mcpemails.com/api/mcp into Claude, Cursor or ChatGPT, authorize, and your agent has the inbox.
Comparing providers first? See the email provider compatibility matrix
What actually goes wrong with Namecheap Private Email
The Namecheap account login is not the mailbox password, and it never will be
The credential you use at namecheap.com to renew domains has nothing to do with mail. Namecheap's own configuration guide asks for the Master or Application password for this email account, which is the password set on the mailbox when it was created, managed from the Private Email area of your dashboard or from the webmail at privateemail.com. This trips up almost everyone who buys a domain and a mailbox in the same order, because both credentials belong to the same purchase and one of them is even the same address.
Two-factor authentication on Private Email is webmail only, and it locks out every mail client
Namecheap documents 2FA for Private Email as protecting the web interface. The moment you enable it, your ordinary mailbox password stops authenticating over IMAP and SMTP, and the refusal arrives as a plain login failure with no mention of the second factor. The fix is an application-specific password: in the Private Email webmail open Settings, then Security, then Application Passwords, pick the client type from the drop-down and generate one. Paste that into mcpemails in place of the mailbox password. If you have never enabled 2FA, no application password exists and none is needed.
The host is mail.privateemail.com for every customer, and Namecheap says not to change it
Unlike a hosting mailbox, Private Email is not on a server named after your domain. Namecheap's configuration article gives mail.privateemail.com for incoming and outgoing alike and adds that it should not be changed. People frequently try mail.theirdomain.com, which is either dead or points at a Namecheap cPanel hosting account with a completely different mailbox on it. A Namecheap domain does not imply a Namecheap mailbox either: Private Email is a separate subscription, and if you never bought it, there is nothing at that address to connect.
The server is Dovecot, and it omits MOVE, UIDPLUS and SPECIAL-USE
The greeting identifies Dovecot and advertises AUTH=PLAIN, AUTH=LOGIN, SASL-IR, IDLE and LITERAL+, but not MOVE, UIDPLUS or SPECIAL-USE. In practice that means three things. Moving a message is carried out as copy, flag and expunge rather than one atomic command. The identifier of the copy is not reported back and must be found by searching the destination folder. And Sent, Drafts, Trash and Junk are recognised by their names rather than by a role flag, so a mailbox whose folders were renamed needs the folder named explicitly.
Known limits with Namecheap Private Email
- Because the server does not advertise MOVE, a move is not atomic. If a connection drops part way through, a message can exist briefly in both folders.
- Private Email is a subscription separate from the domain. Owning a Namecheap domain does not mean you have a Namecheap mailbox to connect.
- mcpemails connects the mailbox. Aliases, forwarders, catch-all rules and mailbox creation stay in the Namecheap Private Email control panel.
Namecheap Private Email and AI: common questions
Does Claude work with Namecheap Private Email?
Not on its own. Claude has no built-in Namecheap connector. Connecting an MCP server such as mcpemails to the mailbox over IMAP gives Claude read, search, send, reply, schedule and organize access to it, and the same connection then works from Cursor, ChatGPT and other MCP clients rather than one.
What are the Namecheap Private Email IMAP and SMTP settings?
Both are mail.privateemail.com. IMAP is port 993 with SSL, and SMTP is port 465 with SSL, with 143 and 587 documented as the STARTTLS alternatives. The username is your full email address and the password is the mailbox password. Namecheap states the hostname should not be changed, and it was confirmed from a live TLS connection.
Why is my Namecheap Private Email password rejected?
The two usual causes are using your Namecheap account login instead of the mailbox password, and having two-factor authentication enabled on the mailbox. With 2FA on, Private Email accepts only an application-specific password over IMAP, and the failure looks exactly like a wrong password. Check both before resetting anything.
How do I create a Namecheap application password?
Sign in to the Private Email webmail at privateemail.com, open Settings, then Security, then Application Passwords. Choose the application or client type from the drop-down and generate a password. Copy it immediately and paste it into mcpemails in place of the mailbox password. You only need one if two-factor authentication is enabled.
Can I use mail.mydomain.com instead of mail.privateemail.com?
No. Private Email mailboxes are not hosted on a server named after your domain, and Namecheap's own documentation says the hostname should not be changed. If mail.yourdomain.com resolves at all it is likely pointing at Namecheap cPanel hosting, which holds a different mailbox with a different password.
Is my Namecheap mail stored on your servers?
No. Messages are fetched live from Private Email over IMAP for each request and handed to your AI client. Credentials are encrypted at rest and message bodies are not retained.
Give your AI a Namecheap Private Email inbox
Connect Namecheap Private Email in minutes. One inbox free forever, no card required.