EarthLink still runs its own mail servers, older than most of the internet and still answering. mcpemails connects one over IMAP so your AI agent can read, search, send, reply and file that mail.
Claude cannot reach an EarthLink mailbox on its own. mcpemails is a hosted MCP server that connects it over IMAP at imap.earthlink.net on port 993, signing in with your full email address and your ordinary email password. EarthLink issues no app-specific passwords and has no client access switch to turn on, so the credential you already use is the credential that works, and the same settings cover the mindspring.com, peoplepc.com and ix.netcom.com addresses EarthLink still hosts. Outgoing mail uses a different hostname, smtpauth.earthlink.net on port 587. One inbox is free, forever.
EarthLink publishes a single IMAP host for every domain it carries. imap.earthlink.net answers on port 993 over TLS, and the username is the whole address with its own domain intact, so a Mindspring or PeoplePC address goes in unchanged. Outgoing mail is the part people get wrong: it does not share the incoming name. Submission runs at smtpauth.earthlink.net on port 587 with STARTTLS, a hostname that exists because EarthLink historically ran a separate unauthenticated relay for customers on its own network and kept the authenticated one under its own name. EarthLink's documentation says to use your full email address and password on both, and there is no app password to create. POP is the one place the domains diverge: EarthLink documents per-domain POP hosts such as pop.mindspring.com, which is why some old setup guides look domain specific when the IMAP side is not.
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.earthlink.net | 993 | TLS (implicit) |
| SMTP (outgoing) | smtpauth.earthlink.net | 587 | STARTTLS |
Verified 2026-08-31: imap.earthlink.net answered a TLS connection and identified itself as an IMAP server under that name. It advertises CRAM-MD5, EL-TAC, EL-VOICE authentication.
Sign in with: Your full address, whichever legacy domain it uses: name@earthlink.net, name@mindspring.com, name@peoplepc.com or name@ix.netcom.com.
Seventeen action-based MCP tools: send, reply, forward, schedule, and organize. Your agent finishes the job inside EarthLink.
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 EarthLink webmail with the address you want to connect and confirm the password works there. EarthLink accounts often carry several mailboxes under one subscription, each with its own password, and the one on the account you pay with is not necessarily the one on the address you are connecting.
In mcpemails choose IMAP / SMTP and enter the address exactly as it is written, name@mindspring.com included. The EarthLink hosts and ports above are prefilled and were verified from a live TLS connection, including the separate outgoing host on port 587.
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
The capability list EarthLink returns before login offers AUTH=CRAM-MD5, AUTH=EL-TAC and AUTH=EL-VOICE, with no AUTH=PLAIN and no AUTH=LOGIN. The last two are EarthLink's own mechanisms and no ordinary mail client implements them. mcpemails reads that list before it signs in. When a server offers mechanisms but not PLAIN, and does not announce LOGINDISABLED, mcpemails uses the IMAP LOGIN command, which is part of base IMAP and needs no advertising. It sends the same address and password PLAIN would, inside the same TLS connection. We probed EarthLink with a made-up account, one attempt per mechanism: LOGIN came back "Login incorrect", the answer of a server that actually checked the credential, while PLAIN and CRAM-MD5 both came back "Server(s) unavailable to complete operation". mcpemails also implements CRAM-MD5, but uses it only on servers that disable LOGIN. What has not been tested yet is a sign-in with a real EarthLink mailbox, so this path is verified against the server's answers, not end to end.
It is smtpauth.earthlink.net, on port 587 with STARTTLS rather than implicit TLS on 465. Guides that pattern-match from the incoming host, or that assume 465 because most providers use it, produce a configuration that connects for reading and silently fails on the first send. If mail arrives but nothing leaves, this is why.
EarthLink does not advertise SASL-IR, and after a rejected sign-in it closes the connection instead of letting the client try another way. That is why mcpemails chooses the mechanism from the capability list before it sends anything, rather than trying PLAIN first and falling back: a wrong first guess would use up the attempt, and repeated failures against a mailbox are worth avoiding. The LOGIN command is a single step, so the missing SASL-IR does not affect it.
The EarthLink IMAP service is old and it shows in its capability list. Without IDLE there is no push, so new mail is found by polling. Without MOVE, filing a message runs as COPY, then STORE the deleted flag, then EXPUNGE. Without SPECIAL-USE the server never says which folder is Sent or Trash, so those are matched by name. UIDPLUS is present, which at least means a copied message reports its new id.
Not directly. Claude has no built-in EarthLink 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 earthlink.net or mindspring.com mail, and the same connection works in Cursor, ChatGPT and other MCP clients.
IMAP is imap.earthlink.net on port 993 with implicit TLS. Outgoing mail is smtpauth.earthlink.net on port 587 with STARTTLS and authentication required. Both were verified from a live TLS connection. EarthLink's own documentation says to use your full email address and email password on both.
For IMAP, yes. EarthLink serves the legacy domains it acquired from the same imap.earthlink.net host, and the username is simply the full address with its own domain. POP is the exception: EarthLink documents per-domain POP hostnames such as pop.mindspring.com, which is why older guides look domain specific.
No. EarthLink issues no app-specific passwords and has no page for creating one. A mail client signs in with the password for that mailbox. Before login EarthLink advertises only CRAM-MD5 and two mechanisms of its own, not PLAIN or LOGIN, which is why some clients refuse to send a correct password at all. mcpemails signs in with the IMAP LOGIN command instead, which EarthLink's server answers as a normal credential check. That has been confirmed with a made-up account only, not yet with a real EarthLink mailbox.
No. Messages are fetched live from EarthLink over IMAP for each request and passed to your AI client. Credentials are encrypted at rest and message bodies are not retained.
Your existing email password is all it takes. One inbox free forever, no card required.