Give your AI agent a real Purelymail inbox. Read, search, send, reply, schedule and organize mail over IMAP with the mailbox's own password, in every MCP client rather than just one.
Claude cannot reach Purelymail on its own. mcpemails is a hosted MCP server that connects it over IMAP at imap.purelymail.com on port 993, so Claude, Cursor or any MCP client can read, search, send and organize that mail. Purelymail has no IMAP switch to find: you authenticate with the mailbox's full email address and that mailbox's own password, or an app password if the mailbox has two-factor authentication turned on. One inbox is free, forever.
Purelymail serves IMAP at imap.purelymail.com on port 993 over TLS, and SMTP at smtp.purelymail.com on port 465, also implicit TLS. There is nothing to enable first. Purelymail treats IMAP, POP3 and SMTP as ordinary access and every mailbox has them from the moment it is created, which already puts it ahead of most webmail providers. What people get wrong here is which credentials they type. Purelymail keeps your account, the login for the management portal and the flat $10 a year bill, separate from your users, which are the mailboxes that actually send and receive. IMAP wants a user: the complete address including the domain, plus that user's own password. This is true whether the address sits on a shared Purelymail domain or on a custom domain you brought yourself, because the hostnames are the same for every customer.
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.purelymail.com | 993 | TLS (implicit) |
| SMTP (outgoing) | smtp.purelymail.com | 465 | TLS (implicit) |
Verified 2026-08-31: imap.purelymail.com answered a TLS connection and identified itself as an IMAP server under that name. It advertises PLAIN authentication.
Sign in with: The mailbox's full address, domain included: you@yourdomain.com, not the Purelymail account name you sign into the portal with.
Nine action-based MCP tools, not just drafts. Your agent finishes the job inside Purelymail.
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. No card is required, and the free plan connects one inbox for as long as you want it.
Sign in to the Purelymail account portal and click User in the top navigation. The address listed there is the username you will use, written out in full with its domain. The account name you signed up with is not a mailbox and will never authenticate over IMAP.
If multi-factor authentication is on for that user, open the user, scroll to App Passwords, click Add New, give it a name and copy the code. Purelymail displays it once. Now choose IMAP / SMTP in mcpemails, enter the full address and that password. The hosts below are prefilled.
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
Purelymail deliberately splits the account that signs into the management portal and pays the bill from the users that hold mail. IMAP and SMTP accept only a user, and only in full: you@yourdomain.com, never a bare local part, and never the account name you picked at signup. The server answers a wrong account name and a wrong password with the same flat authentication failure, so this reads as a typo rather than a category error.
Purelymail lets you deliver info@yourdomain.com into an existing inbox with a routing rule, and a catch-all rule can absorb every address on a domain, with none of those addresses existing as users. Purelymail's own documentation is explicit that you do not need to create user accounts for them. They are delivery targets, not logins, so there is nothing to authenticate against. Connect the user the rule delivers into, and let your agent filter on the To header.
Purelymail forces an app password only on users that have multi-factor authentication switched on, and MFA is configured individually on each user. One mailbox on your account can therefore connect with its ordinary password while another on the same domain rejects it. Check the individual user in the portal before assuming the password is wrong. App passwords live in that user's App Passwords section and are shown only once.
Not directly. Claude has no built-in Purelymail connector and cannot open an IMAP session by itself. Connecting an MCP server such as mcpemails to your Purelymail mailbox gives Claude read, search, send, reply, schedule and organize access to it, and the same connection works in Cursor, ChatGPT and any other MCP client rather than in one app only.
IMAP is imap.purelymail.com on port 993 with implicit TLS. SMTP is smtp.purelymail.com on port 465, also implicit TLS. Log in with the mailbox's full email address and that mailbox's password, or an app password if the user has two-factor authentication enabled. Both hosts were verified from a live TLS connection on the date shown on this page.
No. Purelymail has no IMAP toggle and no paid tier that gates client access, so a mailbox is reachable the moment you create it. If a login fails, the cause is the credentials rather than a setting you have not found yet.
Three causes, in the order worth checking. You are using the Purelymail account name instead of the mailbox address. The address you entered is an alias or catch-all rule rather than a real user. Or that user has multi-factor authentication on, which means only an app password from its App Passwords section will authenticate.
Yes. Purelymail charges nothing extra for users on domains you own, and custom-domain mailboxes use exactly the same imap.purelymail.com and smtp.purelymail.com hosts as addresses on the shared domains. Only the username changes.
No. Messages are fetched live from Purelymail over IMAP for each request and passed to your AI client. Credentials are encrypted at rest; message bodies are not retained after the request that asked for them.
Connect Purelymail in minutes. One inbox free forever, no card required.