Give your AI agent a real Rackspace 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 Rackspace 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.
Rackspace Email connects over IMAP/SMTP with your mailbox password. Both hosts are secure.emailsrvr.com whatever your own domain is, and that is the part people miss: the mail host is not derived from your domain name. Set or reset the mailbox password in the Rackspace Cloud Office control panel.
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) | secure.emailsrvr.com | 993 | TLS (implicit) |
| SMTP (outgoing) | secure.emailsrvr.com | 465 | TLS (implicit) |
Verified 2026-08-31: secure.emailsrvr.com answered a TLS connection and identified itself as an IMAP server under that name. It advertises PLAIN authentication.
Sign in with: Your full email address at your own domain. Rackspace uses the whole address as the login name, not a separate username.
Nine action-based MCP tools, not just drafts. Your agent finishes the job inside Rackspace Email.
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 for mcpemails, no card required. The free plan connects one inbox, forever.
In the Cloud Office control panel, open the mailbox and set its password. Use the secure host, secure.emailsrvr.com, not the unencrypted one.
Choose IMAP / SMTP, add your Rackspace Email address, the hosts below and the password to connect the inbox securely.
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
Rackspace Email serves every customer from secure.emailsrvr.com, for incoming and outgoing alike. mail.yourdomain.com is not a Rackspace name and does not exist unless you created it yourself. Because emailsrvr.com carries no Rackspace branding, people who find it in an old configuration frequently assume it is wrong and replace it with something that looks more plausible, at which point nothing connects. It is correct. Our probe completed a TLS handshake against it and the certificate names secure.emailsrvr.com.
Rackspace app passwords only exist once multi-factor authentication is on, and once it is on, the mailbox password stops working in anything that speaks IMAP or SMTP while continuing to work in webmail. That split is what makes it so confusing: you can log into webmail with the password your client is being refused for. Create an app password from the account security settings in Rackspace webmail or in the Cloud Office control panel, label it for the client it serves, and copy it immediately, because it is displayed once. Losing it means deleting the entry and generating a new one.
Rackspace Email is the standalone IMAP mailbox product and the one this page covers. Rackspace also sells Hosted Exchange, running Exchange on Rackspace's own infrastructure, and resells Microsoft 365, where the mailbox lives on Microsoft's servers under Microsoft's identity platform. Only Rackspace Email answers on secure.emailsrvr.com. We do not claim to connect a Microsoft 365 mailbox, because Microsoft's default tenant policy blocks an ordinary end user from consenting to third-party mail read and write access. If your webmail is Outlook on the web, that is the Microsoft product.
The IMAP greeting names a machine such as proxy7.mail.iad3b.rsapps.net, so connections land on a front-end tier rather than on the store holding your mail. That tier advertises a deliberately small capability set: SASL-IR, IDLE, LITERAL+ and AUTH=PLAIN, with no AUTH=LOGIN, no MOVE, no UIDPLUS and no SPECIAL-USE. The missing AUTH=LOGIN is the one that bites: client libraries hard-wired to the LOGIN mechanism, common in tooling written against Exchange, fail at authentication rather than returning a useful error, while the SMTP side accepts both PLAIN and LOGIN. The same account can therefore succeed at sending and fail at reading in one client.
Not on its own. Claude has no built-in Rackspace 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 because it is plain IMAP the same mailbox is then available in Cursor, ChatGPT and other MCP clients.
Both are secure.emailsrvr.com. IMAP is port 993 with SSL/TLS and SMTP is port 465, also SSL/TLS. The login name is your complete email address and the password is the mailbox password. The host is shared across all Rackspace Email customers rather than built from your domain, and it was confirmed from a live TLS connection.
That specific pattern means multi-factor authentication is enabled on the mailbox. Rackspace keeps accepting the mailbox password on the web while requiring an app password for IMAP and SMTP. Generate one from the account security settings in webmail or the Cloud Office control panel and use it in place of the mailbox password.
App passwords only appear once multi-factor authentication is switched on. With MFA enabled, open your account security settings in Rackspace webmail or in the Cloud Office control panel, find the app passwords area and create one, labelling it for the client it belongs to. It is shown once, so copy it straight away.
Yes. emailsrvr.com is Rackspace's unbranded mail domain and secure.emailsrvr.com is the TLS endpoint every Rackspace Email customer uses. There is no per-domain hostname to look up, and replacing it with a name based on your own domain is the most common reason a Rackspace setup fails to connect at all.
No. Messages are fetched live from Rackspace over IMAP for each request and handed to your AI client. Credentials are encrypted at rest and message bodies are not retained.
Connect Rackspace Email in minutes. One inbox free forever, no card required.