freenet supports IMAP but keeps it behind a switch it would rather you left alone. Flip it once and mcpemails connects the mailbox so your AI agent can read, search, send, reply and file that mail.
Claude cannot reach a freenet.de mailbox on its own. mcpemails is a hosted MCP server that connects it over IMAP at mx.freenet.de on port 993, authenticating with your full address and your freenet Mail password. The one thing you must do first is tick POP3, IMAP und SMTP aktivieren in the mailbox settings, because freenet gates all client access behind that checkbox and recommends leaving it off. Once it is on, Claude, Cursor or any other MCP client can read, search, send and organise that mail, and one inbox is free, forever.
freenet publishes a single server name for everything: mx.freenet.de is the IMAP server and the SMTP server, and it warns in the same table that you should use only the names it gives and never an IP address or an alternative name. IMAP answers on port 993 over TLS and on 143 with STARTTLS; submission runs on 465 with TLS and on 587 with STARTTLS, with SMTP authentication switched on. The username is the whole address and the password is the freenet Mail password. What separates freenet from most providers is the gate in front of all of it. Client access is a checkbox in the mailbox settings labelled POP3, IMAP und SMTP aktivieren, and freenet's own help article recommends deactivating these functions on the grounds that native clients do not support all modern security features. Its advice, your call: while the box is clear, no client of any kind can log in.
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) | mx.freenet.de | 993 | TLS (implicit) |
| SMTP (outgoing) | mx.freenet.de | 465 | TLS (implicit) |
Verified 2026-08-31: mx.freenet.de answered a TLS connection and identified itself as an IMAP server under that name. It advertises LOGIN, PLAIN authentication.
Sign in with: Your full address in the form name@domain, for example max.mustermann@freenet.de. That is freenet's own wording for the Benutzer or Kontoname field.
Nine action-based MCP tools: send, reply, forward, schedule, and organize. Your agent finishes the job inside freenet.
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 at mail.freenet.de, open the settings from the gear icon at the top right, choose POP3/IMAP/SMTP and then Einrichtung POP3/IMAP, and tick the box marked POP3, IMAP und SMTP aktivieren. The same box switches client access back off later if you want it gone.
In mcpemails choose IMAP / SMTP and enter the full address as name@freenet.de with the password for that mailbox. Both directions use mx.freenet.de, which is prefilled here and was verified from a live TLS connection.
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
This is not a dormant setting somebody forgot to enable. freenet's help page opens by saying that native clients such as Outlook and Thunderbird always use POP3, IMAP and SMTP, that those protocols do not support all modern security features and are therefore easier to attack, and that it recommends deactivating the functions in your mailbox. So expect the box to be clear, expect no warning that it is the cause, and expect a correct password to be refused until you tick it.
There is no imap.freenet.de and no smtp.freenet.de. Incoming and outgoing both use mx.freenet.de, which looks wrong to anyone used to the usual prefixes and gets silently corrected by people setting things up from memory. freenet also states in the same table that you should not substitute IP addresses or alternative names, because doing so causes problems in use.
freenet documents the mailbox folders as inbox, sent and drafts, and notes that depending on the client they appear as inbox.sent and inbox.drafts with the inbox as their parent. Because the server does not advertise SPECIAL-USE, nothing tells a client which folder is which, so it has to match those names. Tooling that looks for Sent, Gesendet or Gesendete Objekte finds nothing. Name the folder explicitly if an agent cannot locate it.
The server omits the MOVE extension, so filing a message runs as COPY, then STORE the deleted flag, then EXPUNGE rather than one atomic command, and without UIDPLUS the id of the new copy is not reported back and has to be found by searching the destination folder. IDLE is supported, so new mail does arrive by push rather than polling, which is better than several other providers in this category manage.
Not directly. Claude has no built-in freenet 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 freenet.de mail, and the same connection works in Cursor, ChatGPT and other MCP clients. Client access has to be enabled in the mailbox first.
Both are mx.freenet.de. IMAP is port 993 with implicit TLS or 143 with STARTTLS, and SMTP is port 465 with implicit TLS or 587 with STARTTLS, with SMTP authentication enabled. The username is your full address. The hosts were verified from a live TLS connection on the date shown on this page.
Almost always because POP3, IMAP and SMTP are not activated on the mailbox. freenet keeps client access behind a checkbox in the settings under POP3/IMAP/SMTP, then Einrichtung POP3/IMAP, and recommends leaving it off. While it is off the server refuses correct credentials with an error that reads like a typo.
No. There is no app-specific password to create. A client authenticates with the password of the freenet Mail mailbox itself, once client access is enabled. If you want to revoke a connection, clear the activation checkbox or change the mailbox password.
No. Messages are fetched live from freenet over IMAP for each request and passed to your AI client. Credentials are encrypted at rest and message bodies are not retained.
Tick one box in freenet Mail, then connect. One inbox free forever, no card required.