Soverin + AI

Connect Soverin to Claude,
Cursor, ChatGPT, any MCP client

Give your AI agent a real Soverin inbox. Read, search, send, reply, schedule and organize mail over IMAP, on any MCP client, including mailboxes on your own domain, with an honest account of what protects the connection and what does not.

Claude cannot reach a Soverin mailbox on its own. mcpemails is a hosted MCP server that connects it over IMAP at imap.soverin.net on port 993, and SMTP at smtp.soverin.net on port 465, so Claude, Cursor or any MCP client can read, search, send and organize that mail. Soverin documents your email address as the username and your account password as the password, and those same two hosts serve custom-domain mailboxes as well as soverin.net ones. Soverin issues no app passwords, and its two-factor authentication protects the dashboard and webmail rather than IMAP, so the credential you store here is the account password. One inbox is free, forever.

1 inbox free, forever Your Soverin account password Email fetched live, never stored

How Soverin connects: soverin.net hosts, whatever your address says

Soverin serves IMAP at imap.soverin.net on port 993 with SSL, or 143 with STARTTLS, and SMTP at smtp.soverin.net on port 465 with SSL, or 587 with STARTTLS. Soverin's own help puts it directly: your Soverin email address is also your username, and the password is your account password. The important consequence is that a mailbox on a domain you own still authenticates against the soverin.net hosts. Soverin runs the mail service; your domain only decides what your address looks like and where the MX records point. There is no app-password mechanism here, and Soverin's two-factor authentication is documented as protecting the Soverin Dashboard and the integrated webmail, which means switching it on neither breaks a mail client nor secures one.

The exact Soverin IMAP and SMTP settings

Copy these into the connect form. mcpemails prefills them where it can, and retries the other standard transport if the first does not answer.

ProtocolServerPortSecurity
IMAP (incoming)imap.soverin.net993TLS (implicit)
SMTP (outgoing)smtp.soverin.net465TLS (implicit)

Verified 2026-08-31: imap.soverin.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 Soverin email address in full, including a custom domain: name@yourdomain.eu. Soverin documents the address as the username.

What your AI can do

A Soverin inbox your agent can actually use

Nine action-based MCP tools: send, reply, forward, schedule, and organize. Your agent finishes the job inside Soverin.

  1. 01Read

    Read & search mail

    List, read and search across folders to find that invoice, summarize a thread, or pull the latest from a sender.

  2. 02Send

    Send, reply & forward

    Compose and send real messages, reply in-thread, and forward, directly from your mailbox, not as a draft you finish by hand.

  3. 03Schedule

    Schedule for later

    Queue a message to go out at the right time, so your agent can draft now and send on schedule.

  4. 04Organize

    Move, copy, flag, archive, delete

    Keep the inbox tidy: file mail into folders, flag what matters, archive the rest, or delete on request.

Setup

Connect Soverin in four steps

From sign-up to first AI email in a couple of minutes.

01

Create your free mcpemails account

Sign up at mcpemails.com. The free plan connects one inbox, forever, with no card. You get an MCP URL and a key at the end of it.

02

Confirm the address the mailbox authenticates as

In the Soverin Dashboard, open the mailbox you want to connect. The address on the mailbox itself is the username, not one of the aliases you have pointed at it. Soverin gives every mailbox unlimited aliases, so it is easy to have stopped using the original address years ago and to no longer think of it as the login.

03

Add the mailbox in mcpemails

Choose IMAP / SMTP, enter that full address and your Soverin account password. The hosts are prefilled at imap.soverin.net and smtp.soverin.net and were verified from a live TLS connection. Do not substitute a hostname built from your own domain; the certificate is issued for Soverin's own name and a client that validates strictly will refuse it.

04

Paste the MCP URL into your AI

Drop https://mcpemails.com/api/mcp into Claude, Cursor or ChatGPT, authorize, and your agent has the inbox.

Before you start

What actually goes wrong with Soverin

Two-factor authentication does not reach IMAP, and no app password exists

Soverin's own 2FA article scopes the feature to two places: the Soverin Dashboard, for managing your account and settings, and the integrated webmail. IMAP, POP and SMTP are not on that list, and Soverin publishes no app-password mechanism to go with it. Two practical results. Turning 2FA on will not break this connection or any other mail client, the opposite of what happens at Runbox or Posteo. And 2FA is not what limits a connected client here: the only credential is your account password, so revoking a connection means changing that password and re-entering it everywhere. Keep the recovery code Soverin issues, because losing the authenticator without it means losing dashboard access.

The IMAP server offers no AUTH=LOGIN, while SMTP does

Soverin's IMAP banner advertises AUTH=PLAIN, AUTH=OAUTHBEARER and AUTH=XOAUTH2, with no AUTH=LOGIN. The SMTP server accepts PLAIN and LOGIN both. Clients hard-wired to the LOGIN mechanism, common in tooling originally written against Exchange, therefore fail to read while sending fine from the same account with the same credentials, which is a confusing thing to debug. The two OAuth mechanisms belong to Soverin's own platform integrations and a third party cannot obtain a token for them, so password authentication is the route.

A custom domain does not give you a mail host of your own

Soverin sells mailboxes on domains you own, and the natural assumption is that mail.yourdomain.eu must therefore be the server. It is not. Your MX records point into Soverin's infrastructure, and clients authenticate against imap.soverin.net and smtp.soverin.net exactly as a soverin.net address would. The certificate on those hosts is issued for Soverin's own name, so pointing a client at a hostname on your domain produces a certificate mismatch rather than a working connection.

No MOVE, no UIDPLUS, no SPECIAL-USE

The Dovecot server advertises IDLE and SASL-IR but not MOVE, UIDPLUS or SPECIAL-USE. Filing a message is a COPY, a STORE of the \Deleted flag and an EXPUNGE rather than one command, and with no UIDPLUS the server does not report the new UID, so the moved copy is found again by searching the destination. Folder roles come from names because nothing on the wire declares them, so a renamed or Dutch-named Sent or Trash folder may need to be named explicitly when you ask an agent to file something.

Known limits with Soverin

  • Connecting a Soverin mailbox to an AI client means that AI provider reads the content of the messages it works with. mcpemails fetches mail live from imap.soverin.net for each request and does not store message bodies, and credentials are encrypted at rest, but the text still reaches Claude, Cursor or whichever client you connect. Soverin's EU-only hosting, its subscription funding and its commitment not to scan or profile your mail all describe Soverin. None of them travel with a message into an AI vendor you attach yourself.
  • There is no scoped credential. Soverin has no app passwords, so what is stored here is your account password, the same one that opens the Soverin Dashboard. Withdrawing this connection means changing that password rather than deleting a single token.
  • mcpemails connects the mailbox, not the account. Aliases, additional mailboxes, domain settings and forwarding stay in the Soverin Dashboard and are not visible to or changeable by your AI client.
FAQ

Soverin and AI: common questions

Does Claude work with Soverin?

Not directly. Claude has no Soverin connector and cannot speak IMAP by itself. Connecting an MCP server such as mcpemails to your Soverin mailbox gives Claude read, search, send, reply, schedule and organize access over IMAP, and the same connection then works in Cursor, ChatGPT and other MCP clients without repeating the setup.

What are the Soverin IMAP and SMTP settings?

IMAP is imap.soverin.net on port 993 with SSL, or 143 with STARTTLS. SMTP is smtp.soverin.net on port 465 with SSL, or 587 with STARTTLS. The username is your Soverin email address in full and the password is your account password. Both hosts were verified from a live TLS connection and both serve custom-domain mailboxes too.

Does Soverin have app passwords, and does 2FA cover IMAP?

No to both. Soverin publishes no app-password mechanism for mail clients, and its two-factor authentication is documented as covering the Soverin Dashboard and the integrated webmail. IMAP and SMTP continue to accept your account password whether 2FA is on or off, so enabling it will not disturb this connection and will not restrict it either.

I use Soverin on my own domain. Which host do I use?

The same ones: imap.soverin.net and smtp.soverin.net. A custom domain changes your address and your MX records, not the servers your client authenticates against. Building a hostname from your own domain gives you a certificate that does not match, which most clients refuse outright and which no client should be told to ignore.

Why can a client read my Soverin mail but not send, or the other way round?

Usually the authentication mechanism. Soverin's IMAP server offers PLAIN but not LOGIN, while its SMTP server offers both, so a client fixed on the LOGIN mechanism fails on one side and works on the other with identical credentials. Configure both sides for normal password authentication inside the TLS connection rather than for a named mechanism.

Is my Soverin mail stored on your servers?

No. Messages are fetched live from imap.soverin.net over IMAP for each request and passed to your AI client. Credentials are encrypted at rest and message bodies are not retained. The AI client you connect does receive the content of whatever it reads, which is the decision worth making deliberately rather than the storage question.

Give your AI a Soverin inbox

Connect Soverin in minutes, custom domains included. One inbox free forever, no card required.