SAPO puts mail-client access on its Premium tier. If your account has it, an AI agent can read, search, send, reply, schedule and organize the mailbox over IMAP.
Claude cannot reach a SAPO mailbox on its own, and on a free SAPO Base account neither can anything else: SAPO states in its own documentation that o acesso IMAP/POP está disponível apenas para contas Premium. On a Premium account, mcpemails is a hosted MCP server that connects the mailbox over IMAP at imap.sapo.pt on port 993 with your SAPO address and password, so Claude, Cursor or any MCP client can read, search, send and organize the mail. There is no app password and no toggle to switch on: the gate is the plan. One inbox on mcpemails is free, forever.
SAPO serves IMAP at imap.sapo.pt on port 993 over implicit TLS and SMTP submission at smtp.sapo.pt on port 465, with authentication required. Its own configuration page words the hosts as imap.sapo.pt para endereços terminados @sapo.pt, and the credential as o seu endereço de e-mail SAPO e a respetiva password. There is no app-specific password and no per-mailbox client-access switch. The one thing that decides whether any of this works is the plan on the account. SAPO's help pages state the restriction directly: O acesso por IMAP, POP e SMTP só está disponível para contas Premium. A free Base account keeps its mail and its webmail at mail.sapo.pt and loses the protocols, which means every desktop and mobile mail client, and every hosted MCP server including this one.
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.sapo.pt | 993 | TLS (implicit) |
| SMTP (outgoing) | smtp.sapo.pt | 465 | TLS (implicit) |
Verified 2026-08-31: imap.sapo.pt answered a TLS connection and identified itself as an IMAP server under that name. It advertises PLAIN authentication.
Sign in with: Your full address, including the domain: nome@sapo.pt.
Seventeen action-based MCP tools: send, reply, forward, schedule, and organize. Your agent finishes the job inside SAPO.
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 forever and does not ask for a card.
Sign in at mail.sapo.pt and look at the plan on the account. Base is the free tier and has no IMAP, POP or SMTP: it is webmail and the SAPO app only. Premium restores the protocols along with the larger mailbox and no advertising. This is a billing state and not a setting, so there is nothing in the mail options screen that will change it.
SAPO issues no application-specific password. The credential is your ordinary SAPO password with the complete address as the username, used on both the incoming and the outgoing side. If the webmail accepts it and the client does not, the account is almost certainly on the Base tier rather than Premium.
Choose IMAP / SMTP, enter the full address such as nome@sapo.pt, and enter the password. The SAPO hosts and ports are prefilled and were verified from a live TLS connection. Then 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
imap.sapo.pt is up, completes a TLS handshake and greets you with Welcome to PTMail regardless of who is asking. That makes the Premium restriction genuinely hard to diagnose, because every symptom points at credentials. If the SAPO webmail accepts your password and a mail client does not, stop testing the password. The plan is the difference. This applies identically to Outlook, Thunderbird, Apple Mail, the phone clients and every MCP server, ours included: no third-party tool can grant protocol access that the account does not have.
SAPO hibernates free Base accounts that go unused for more than 90 days: as contas Base inativas por mais de 90 dias são hibernadas, deixando de receber mensagens, and content on a hibernated account may be removed. Premium accounts are never hibernated. This matters specifically for the tempting idea of creating a spare SAPO address to hand to an agent and then forgetting about it. A Base account you do not sign into stops being a working mailbox.
The IMAP banner offers AUTH=PLAIN and nothing else, with no AUTH=LOGIN. Client libraries hard-wired to the LOGIN mechanism, which is common in tooling written against Exchange, are refused at the authentication step with an error that reads like bad credentials. The SMTP side accepts both PLAIN and LOGIN, so the two halves of the same account can behave differently inside one client. mcpemails negotiates whatever each leg actually offers.
The server does not advertise the IMAP MOVE extension, so filing a message runs as a copy, a flag update and an expunge rather than one atomic command. It omits SPECIAL-USE too, so Sent, Drafts and Trash are matched by name rather than by role. A Portuguese SAPO mailbox usually names them Enviadas, Rascunhos and Lixo, so name the folder explicitly if an agent cannot find it.
Only on a Premium account. SAPO restricts IMAP, POP and SMTP to Premium, so a free Base account cannot be connected by any mail client or MCP server. With Premium, pointing mcpemails at the mailbox gives Claude read, search, send, reply, schedule and organize access, and the same connection works from Cursor and ChatGPT.
IMAP is imap.sapo.pt on port 993 with SSL. SMTP is smtp.sapo.pt on port 465 with SSL and authentication required. The username is your complete sapo.pt address and the password is your SAPO password. Both hosts were confirmed from a live TLS connection and match what SAPO publishes.
Because IMAP and POP access moved to the Premium tier. SAPO's own help states that IMAP and POP are available only for Premium accounts. A free Base account keeps webmail at mail.sapo.pt and the SAPO app, and loses every protocol a desktop or mobile client would use.
No. SAPO publishes no application-specific password mechanism. Mail clients authenticate with the ordinary SAPO account password together with the complete address, on both the incoming and the outgoing server. If that password works in the webmail but not in a client, the cause is the account tier rather than the credential.
Free Base accounts inactive for more than 90 days are hibernated and stop receiving messages, and their content may be removed. Accounts over their storage limit for more than 90 days are treated the same way. Premium accounts are not hibernated. Do not park an unused Base address as a dedicated agent mailbox.
No. Messages are fetched live from SAPO over IMAP for each request and handed to your AI client. Credentials are encrypted at rest and message bodies are not retained.
If your SAPO account is Premium, connect it in minutes. One inbox free forever, no card required.