Give your AI agent a real GMX inbox in minutes. Read, search, send, reply, schedule and organize mail with IMAP and your account password, and use the same inbox in every MCP client, not just one.
Claude cannot reach GMX on its own. mcpemails is a hosted MCP server that connects it over IMAP using your account 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.
GMX connects over IMAP/SMTP, but POP3 and IMAP access is switched off by default. Turn it on in GMX under E-mail settings, POP3/IMAP retrieval, then connect with your GMX address and password. If GMX asks you to create an application-specific password, use that instead. German accounts use the .net hosts, imap.gmx.net and mail.gmx.net.
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.gmx.net | 993 | TLS (implicit) |
| SMTP (outgoing) | mail.gmx.net | 465 | TLS (implicit) |
Verified 2026-08-31: imap.gmx.net answered a TLS connection and identified itself as an IMAP server under that name. It advertises LOGIN, PLAIN authentication.
Sign in with: Your full GMX Mail address, including the domain: name@gmx.net, name@gmx.com, name@gmx.de or name@gmx.at.
Nine action-based MCP tools, not just drafts. Your agent finishes the job inside GMX.
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 GMX, open E-mail settings, POP3/IMAP retrieval, and allow POP3 and IMAP access. GMX switches it off again if the account goes unused for a long time.
Choose IMAP / SMTP, add your GMX 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
External access to a GMX Mail account is deactivated until you enable it: open the Email tab, then Settings, then POP3 & IMAP, tick Enable access to this account via POP3 and IMAP, and save. GMX documents something people rarely notice on the way past: it turns the permission off again automatically, for security, if the mailbox goes a long stretch with no POP3 or IMAP activity. So a connection that has worked for months can stop with a login failure while nothing at all has changed on your side. The setting does not appear in the GMX phone app either, so you have to do this in a browser.
GMX breaks the naming convention almost every other provider follows. Incoming is imap.gmx.net, but outgoing submission is mail.gmx.net on port 465. A guessed smtp.gmx.net does not answer, and clients that fill hostnames in by pattern get this wrong every time. Both names on this page were confirmed by opening a live TLS connection to them, and the certificate GMX presents is issued for mail.gmx.net.
GMX Mail's submission server announces a maximum message size of roughly 135 MB, which is by a wide margin the largest of any provider on this site. That is a ceiling on what GMX will take from you, not a promise of delivery. The receiving server applies its own limit, and most sit somewhere between 10 MB and 50 MB, so a large attachment that GMX cheerfully accepts can still bounce minutes later from the other end. If an agent is sending something big, share a link instead.
With two-factor authentication off, your ordinary GMX password works in a mail client as soon as the POP3 and IMAP box is ticked. If you have two-factor authentication enabled and GMX asks you for an application-specific password, use that instead: the ordinary password stops working in external programs at that point, and the failure looks like a typo rather than a policy change. GMX's IMAP offers only the PLAIN and LOGIN mechanisms, with no OAuth path, so the credential is always a password of one kind or the other.
Not on its own. Claude has no built-in GMX connector. Connecting an MCP server such as mcpemails to your GMX mailbox over IMAP gives Claude read, search, send, reply, schedule and organize access to it, and the same connection works from Cursor, ChatGPT and other MCP clients. You have to enable POP3 and IMAP access in GMX first.
IMAP is imap.gmx.net on port 993 with implicit TLS. Outgoing mail goes to mail.gmx.net on port 465, also implicit TLS, and not to a host called smtp.gmx.net, which does not exist. The username is your full GMX address. Both hosts were confirmed from a live TLS connection on the date shown on this page.
Sign in to GMX in a web browser, open the Email tab, click Settings, then POP3 & IMAP, and tick the box that enables access to the account via POP3 and IMAP. Save. The option is not present in the GMX mobile app. Until this is on, GMX refuses every mail-client login and the error looks exactly like a wrong password.
GMX documents that it deactivates POP3 and IMAP access automatically, for security reasons, when a mailbox goes a long time without using those protocols. Nothing on your side has to change for this to happen. Sign in through a browser, re-tick the POP3 and IMAP box in Settings, and the connection works again with the same password.
No. Messages are fetched live from GMX over IMAP for each request and handed to your AI client. Credentials are encrypted at rest and message bodies are not retained. Turning POP3 and IMAP access back off in GMX cuts the connection at their end immediately.
Connect GMX in minutes. One inbox free forever, no card required.