Give your AI agent a real A1 inbox. Read, search, send, reply, schedule and organize mail over IMAP, with the one secure host A1 publishes for Austria's a1.net and aon.at addresses.
Claude cannot reach an A1 mailbox on its own. MCPEmails is a hosted MCP server that connects it over IMAP at securemail.a1.net on port 993, authenticating with your full address and your A1 mailbox password, so Claude, Cursor or any MCP client can read, search, send and organize the mail. A1 documents a single host, securemail.a1.net, for everything encrypted: IMAP on 993 with SSL and SMTP on 587 with STARTTLS. There is no app password and nothing to enable first. One inbox is free, forever.
A1 publishes its settings for encrypted connections only, and they all point at the same name. The incoming server is securemail.a1.net on port 993 with the connection type SSL, and the outgoing server is securemail.a1.net on port 587 with the connection type STARTTLS. Port 465 is not offered: it did not answer at all when probed, so a client that insists on implicit TLS for sending waits for a greeting that never comes. The same host and ports serve @a1.net and @aon.at addresses, which is also how the Mozilla autoconfiguration entry that Thunderbird uses for both domains describes them, with the full address as the username and ordinary password authentication. A1's SMTP help adds one note: when you send from a network that is not A1's own, SMTP authentication must be switched on in the account settings. MCPEmails always authenticates on the outgoing server, so that condition is met from the start.
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) | securemail.a1.net | 993 | TLS (implicit) |
| SMTP (outgoing) | securemail.a1.net | 587 | STARTTLS |
Verified 2026-11-04: securemail.a1.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 address, name@a1.net or name@aon.at. A1's own server page lists only the hosts; the Mozilla database entry that mail clients use for both domains records the full address as the username.
21 action-based MCP tools: send, reply, forward, schedule, and organize. Your agent finishes the job inside A1.
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.
The username is your full address, name@a1.net or name@aon.at, and the password is the one for that mailbox. There is no separate mail-program password to create and nothing to switch on in A1 Webmail first.
Choose IMAP / SMTP, enter the address and the password. The host securemail.a1.net is prefilled for both directions, with 993 and SSL for IMAP and 587 and STARTTLS for SMTP, and was verified from a live TLS connection.
Drop https://mcpemails.com/api/mcp into Claude, Cursor or ChatGPT, authorize, and your agent has the inbox.
Step-by-step guides: How to connect Claude to your email · Claude IMAP connector guide
More guides: Custom connectors in Claude, explained · Schedule an email from the chat
Use this inbox in your AI app: Claude · ChatGPT · Cursor · VS Code · Codex · Claude Code · Cline · Windsurf · Gemini CLI · All supported apps
Need the server names and ports? Look up IMAP and SMTP settings
Comparing providers first? See the email provider compatibility matrix
ChatGPT reaches A1 through a custom MCP server, which you add on chatgpt.com with ChatGPT Go or a paid plan.
https://mcpemails.com/api/mcp under Connection, choose OAuth, confirm, click Create as a plugin and sign in to MCPEmails.Most providers on this site accept implicit TLS on port 465 for sending. A1 does not: its documented outgoing setting is port 587 with STARTTLS, and port 465 on securemail.a1.net did not answer when we probed it. A client configured for 465 hangs until it times out rather than getting an error about settings. MCPEmails uses 587 with STARTTLS, which is the pair A1 publishes.
Older A1 configuration guides, including PDFs still downloadable from a1.net, name imap.a1.net for incoming mail and describe unencrypted setups. A1's current server page lists only securemail.a1.net and only encrypted ports. If an existing client of yours still works with the old name, leave it, but for a new connection use the name A1 documents today, which is also the one whose certificate we validated.
A1's help on sending from a foreign Wi-Fi says to enable SMTP authentication in the account settings, or to use A1 Webmail instead. The advice exists because a mail program on a home A1 line can send without logging in, and that stops working elsewhere. Mail your agent sends through MCPEmails leaves from MCPEmails' servers, not from an A1 line, so it is always authenticated with your address and password. No change on your side is needed.
The Dovecot server behind securemail.a1.net advertises IDLE but neither MOVE, UIDPLUS nor SPECIAL-USE. Filing a message runs as a copy, a flag update and an expunge rather than one command, and the sent, drafts and trash folders are identified by their names rather than by a role the server declares. If an agent cannot find your Gesendet or Papierkorb folder, name it in the instruction.
Not on its own. Claude has no built-in A1 connector. Pointing an MCP server such as MCPEmails at the mailbox over IMAP gives Claude read, search, send, reply, schedule and organize access to it, and the same connection then works from Cursor, ChatGPT and other MCP clients.
IMAP is securemail.a1.net on port 993 with SSL. SMTP is securemail.a1.net on port 587 with STARTTLS. Log in with your full address and your mailbox password. A1 documents the same host for a1.net and aon.at addresses, and it was confirmed from a live TLS connection on the date shown on this page.
Yes. The Mozilla autoconfiguration entry for A1 lists a1.net and aon.at together, with securemail.a1.net on 993 for IMAP and 587 with STARTTLS for SMTP and the full address as the username, which matches A1's own server page.
Because A1 does not offer implicit TLS on 465; the port did not answer when probed, so a client waits until it times out. A1 documents outgoing mail on port 587 with STARTTLS, which is what MCPEmails uses.
No. A1 has no app-specific password scheme. Your mailbox password authenticates both IMAP and SMTP.
No. Messages are fetched live from A1 over IMAP for each request and handed to your AI client. Credentials are encrypted at rest and message bodies are not retained.
Yes, once A1 is connected to MCPEmails. On chatgpt.com, add a custom MCP server with the URL https://mcpemails.com/api/mcp and OAuth sign-in. That works with ChatGPT Go and paid plans. ChatGPT gets only the access you approve, and your mail is fetched live, never stored.
Connect your A1 or aon.at mailbox in minutes. One inbox free forever, no card required.