Connect your Ziggo mailbox
to Claude, Cursor, any MCP client
Give your AI agent a real Ziggo inbox. Read, search, send, reply, schedule and organize mail over IMAP with the e-mailwachtwoord you set in Mijn Ziggo.
Claude cannot reach a Ziggo mailbox on its own. mcpemails is a hosted MCP server that connects it over IMAP at imap.ziggo.nl on port 993, authenticating with your full address and the e-mailwachtwoord you set for that address in Mijn Ziggo, so Claude, Cursor or any MCP client can read, search, send and organize the mail. Ziggo has no app password and no client-access toggle, but outgoing mail is the exception in this category: it runs STARTTLS on smtp.ziggo.nl port 587, not implicit TLS on 465. One inbox is free, forever.
How Ziggo connects: IMAP on 993, but STARTTLS for sending
Ziggo serves IMAP at imap.ziggo.nl on port 993 with TLS, and SMTP submission at smtp.ziggo.nl on port 587 using STARTTLS. That split matters more than it sounds. Almost every other consumer provider in this category takes implicit TLS on 465 for submission, so a client or script that hard-codes 465 as the secure port will read a Ziggo mailbox perfectly and then hang or fail on the first send. Ziggo's own server settings page states the pair exactly this way: serverpoort 993, type versleuteling TLS/SSL for incoming, and serverpoort 587, type versleuteling STARTTLS, TLS of SSL for outgoing. Authentication is the same on both legs: gebruikersnaam: volledig e-mailadres and wachtwoord: je e-mailwachtwoord, the password attached to that specific mail address rather than your Mijn Ziggo sign-in.
The exact Ziggo 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.
| Protocol | Server | Port | Security |
|---|---|---|---|
| IMAP (incoming) | imap.ziggo.nl | 993 | TLS (implicit) |
| SMTP (outgoing) | smtp.ziggo.nl | 587 | STARTTLS |
Verified 2026-08-31: imap.ziggo.nl 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: naam@ziggo.nl.
A Ziggo inbox your agent can actually use
Seventeen action-based MCP tools: send, reply, forward, schedule, and organize. Your agent finishes the job inside Ziggo.
- 01Read
Read & search mail
List, read and search across folders to find that invoice, summarize a thread, or pull the latest from a sender.
- 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.
- 03Schedule
Schedule for later
Queue a message to go out at the right time, so your agent can draft now and send on schedule.
- 04Organize
Move, copy, flag, archive, delete
Keep the inbox tidy: file mail into folders, flag what matters, archive the rest, or delete on request.
Connect Ziggo in four steps
From sign-up to first AI email in a couple of minutes.
Create your free mcpemails account
Sign up at mcpemails.com. The free plan connects one inbox forever and does not ask for a card.
Set or reset the e-mailwachtwoord in Mijn Ziggo
Mail addresses, aliases and their passwords are all managed in Mijn Ziggo, on the screen Ziggo labels E-mailadressen beheren. That is where you create an extra address or set a new password for an existing one. The password on the mail address is the credential the IMAP server checks, so if nobody remembers it, set a fresh one there.
Decide which address the agent gets
With an internet subscription Ziggo lets you create up to six e-mail addresses; a telephone-only subscription gets one. If you would rather not hand an agent your primary address, make a second one in Mijn Ziggo and connect that instead. Note that the primary address is tied to the internet subscription and lapses if you cancel it.
Paste it into mcpemails, then paste the MCP URL into your AI
Choose IMAP / SMTP, enter the full address such as naam@ziggo.nl, and paste the e-mailwachtwoord. The Ziggo hosts and ports are prefilled, including the STARTTLS submission port, 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
What actually goes wrong with Ziggo
Sending is STARTTLS on 587, and assuming 465 is the most common Ziggo failure
Ziggo is the odd one out among European consumer providers here. Incoming mail is implicit TLS on 993 like everybody else, so reading works immediately and gives you false confidence. Outgoing mail is smtp.ziggo.nl on 587, where the connection starts in the clear and is upgraded with the STARTTLS command. Point a client at 465 expecting a TLS handshake and you get a stalled connection or a timeout rather than a clean protocol error, and the symptom (reading fine, sending broken) sends people hunting through credentials that were never wrong.
The IMAP banner is two capabilities long, and one of them is the protocol name
Ziggo answers with * OK [CAPABILITY IMAP4rev1 AUTH=PLAIN] VodafoneZiggo server ready. and nothing more. No IDLE, so new mail is only ever discovered by polling and never pushed. No UIDPLUS, so a copied message does not report its new UID back. No MOVE, so filing is copy plus flag plus expunge. No SPECIAL-USE, so folders are matched by name. No SASL-IR either, so the credential goes in a separate step. This is the barest capability set of any provider on this site, and while none of it stops an agent working, it does mean bulk organizing takes more round trips against Ziggo than against almost anything else.
The e-mailwachtwoord is not your Mijn Ziggo login
Ziggo's server settings page is specific: the password for a mail client is je e-mailwachtwoord, the one attached to that individual address. Mijn Ziggo has its own sign-in. Because both are managed in the same portal, people reach for the account password first and get an authentication failure that says nothing useful. If you are not certain which is which, reset the mail password under E-mailadressen beheren and use the value you just set.
The mailbox is tied to the subscription, not to you
Your primary Ziggo address exists because of the internet subscription behind it, and it lapses when that subscription ends. If an agent workflow is going to depend on this mailbox, that is a dependency worth being deliberate about: an address on a domain you control, or on a provider you pay directly, does not disappear when you switch broadband supplier.
Known limits with Ziggo
- Outgoing messages are capped at roughly 30 MB of encoded message, so a large attachment forwarded by an agent can be rejected at the SMTP step.
- Without IDLE, an instruction like tell me as soon as a reply lands is bounded by how often the mailbox is polled rather than by Ziggo's delivery speed.
- Because the server has no MOVE support, a move is not atomic. If a connection drops mid-operation a message can briefly exist in both folders.
Ziggo and AI: common questions
Does Claude work with Ziggo mail?
Not on its own. Claude has no built-in Ziggo 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.
What are the Ziggo IMAP and SMTP settings?
IMAP is imap.ziggo.nl on port 993 with TLS/SSL. SMTP is smtp.ziggo.nl on port 587 with STARTTLS, not implicit TLS on 465. The username is your complete e-mail address and the password is your e-mailwachtwoord. Both hosts were confirmed from a live connection and match Ziggo's published server settings.
Why can I read Ziggo mail but not send it?
Almost always the submission port. Ziggo uses STARTTLS on 587 rather than implicit TLS on 465, so a client configured for 465 completes the IMAP side and then stalls on the SMTP side. Change the outgoing port to 587 with STARTTLS and use the same address and e-mailwachtwoord for outgoing authentication.
Does Ziggo need an app password?
No. Ziggo issues no application-specific passwords. Mail clients authenticate with the e-mailwachtwoord set on that individual mail address in Mijn Ziggo. That is a different credential from your Mijn Ziggo account sign-in, which is why the account password is refused.
How many Ziggo e-mail addresses can I have?
With an internet subscription you can create up to six addresses in Mijn Ziggo; with a telephone-only subscription, one. Extra addresses and aliases are created and given their passwords on the E-mailadressen beheren screen, which makes it easy to give an agent its own address rather than your main one.
Is my Ziggo mail stored on your servers?
No. Messages are fetched live from Ziggo over IMAP for each request and handed to your AI client. Credentials are encrypted at rest and message bodies are not retained.
Give your AI a Ziggo inbox
Connect Ziggo mail in minutes, on the right ports. One inbox free forever, no card required.