Give your AI agent a real att.net or sbcglobal.net inbox. Read, search, send, reply, schedule and organise mail over IMAP using an AT&T secure mail key, in every MCP client rather than one.
Claude cannot reach an AT&T Mail inbox on its own. mcpemails is a hosted MCP server that connects att.net, sbcglobal.net, bellsouth.net and the other AT&T domains over IMAP at imap.mail.att.net on port 993, authenticating with a 16 character secure mail key you create in myAT&T rather than with your AT&T password. Once it is connected, Claude, Cursor or any other MCP client can read, search, send, reply and organise that mail. One inbox is free, forever.
AT&T Mail runs on Yahoo infrastructure, but the credential is issued by AT&T. IMAP answers at imap.mail.att.net on port 993 over TLS and SMTP at smtp.mail.att.net on port 465, also implicit TLS. AT&T stopped accepting the account password from mail apps that do not speak its OAuth flow: instead you generate a secure mail key, a 16 character code, in myAT&T, and type that into the password field. The key never expires, changing your AT&T password does not invalidate it, and you can create a separate one for each app or device so revoking one does not disturb the others. The same hosts and the same key mechanism cover every AT&T mail domain, including sbcglobal.net, bellsouth.net, ameritech.net, pacbell.net and currently.com.
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.mail.att.net | 993 | TLS (implicit) |
| SMTP (outgoing) | smtp.mail.att.net | 465 | TLS (implicit) |
Verified 2026-08-31: imap.mail.att.net answered a TLS connection and identified itself as an IMAP server under that name. It advertises OAUTHBEARER, PLAIN, XOAUTH2 authentication.
Sign in with: Your full AT&T address, whichever domain it ends in: name@att.net, name@sbcglobal.net, name@bellsouth.net and the other AT&T domains all use the same login field.
Nine action-based MCP tools: send, reply, forward, schedule, and organize. Your agent finishes the job inside AT&T Mail.
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 does not ask for a card.
Sign in to your AT&T profile, open the secure mail key section, choose the email address you are connecting, select Add secure mail key, give it a nickname such as mcpemails, and select Create. AT&T shows the 16 character key once. Copy it before you leave the page.
In mcpemails choose IMAP / SMTP, enter your full AT&T address, and paste the secure mail key into the password field. Every AT&T domain uses imap.mail.att.net and smtp.mail.att.net, so the hosts are prefilled for you.
Drop https://mcpemails.com/api/mcp into Claude, Cursor or ChatGPT, authorise, and your agent has the inbox.
Comparing providers first? See the email provider compatibility matrix
AT&T splits mail clients into two groups. Apps AT&T has integrated with its OAuth sign-in get a browser prompt and never see a password. Everything else, mcpemails included, has to present a secure mail key. If you paste your AT&T account password you get an authentication failure that looks identical to a typo, and no amount of resetting the account password will fix it.
AT&T Mail has been served from Yahoo infrastructure for years, and the IMAP banner is Yahoo's. That leads people to Yahoo's account security page to create an app password. It will not help. The credential for an att.net or sbcglobal.net address is issued by AT&T in myAT&T, not by Yahoo.
A secure mail key is bound to a single AT&T email address. If your household has subaccounts on the same AT&T ID, each address you want to connect needs a key created against that address. Reusing the primary account's key for a subaccount fails.
The SMTP host we verified opens the TLS session immediately on port 465 and does not advertise STARTTLS on that port. Older AT&T setup guides that tell you to tick STARTTLS alongside port 465 describe a combination this host will not complete. mcpemails uses implicit TLS on 465, which is what the server actually offers.
Not directly. Claude has no built-in AT&T connector. Connecting an MCP server such as mcpemails to the mailbox over IMAP gives Claude read, search, send, reply, schedule and organise access to your att.net or sbcglobal.net mail, and the same connection works in Cursor, ChatGPT and other MCP clients.
IMAP is imap.mail.att.net on port 993 with implicit TLS. SMTP is smtp.mail.att.net on port 465, also implicit TLS. The username is your full AT&T email address and the password field takes a secure mail key. Both hosts were verified from a live TLS connection on the date shown on this page.
It is a 16 character code that stands in for your password in mail apps that do not use AT&T's OAuth sign-in. You create it in your myAT&T profile, one per email address, and give each one a nickname. It never expires, and changing your AT&T password does not break it.
Yes. AT&T runs att.net, sbcglobal.net, bellsouth.net, ameritech.net, pacbell.net and currently.com addresses on the same platform. They share the same IMAP and SMTP hosts and the same secure mail key requirement, so nothing on this page changes with the domain.
That message usually means the app was set up before AT&T required secure mail keys and is still sending the account password. Create a key in myAT&T and replace the stored password with it. If you had already created a key and later deleted it in your profile, generate a new one; a deleted key stops working immediately.
No. Messages are fetched live from AT&T over IMAP for each request and passed to your AI client. Credentials, the secure mail key included, are encrypted at rest, and message bodies are not retained.
Connect att.net or sbcglobal.net in minutes with a secure mail key. One inbox free forever, no card required.