Give your AI agent a real Titan inbox. Read, search, send, reply, schedule and organize mail over IMAP, in every MCP client rather than just one.
Claude cannot reach Titan Email on its own. mcpemails is a hosted MCP server that connects it over IMAP at imap.titan.email on port 993, so Claude, Cursor or any MCP client can read, search, send and organize that mail. Titan turns every third-party client away until you switch on Enable Titan on Other Apps in webmail settings, and a mailbox with two-factor authentication needs a Titan application password rather than the normal one. One inbox is free, forever.
Titan serves IMAP at imap.titan.email on port 993 over TLS, and SMTP at smtp.titan.email on port 465, also implicit TLS. Two things come first. Third-party access is off on a Titan mailbox until somebody turns it on, and nothing gets past the login before then. And Titan is sold under other companies' brands, so where you bought the mailbox decides which hostnames you use. Many people arrive here unsure the mailbox is Titan at all, because the host that sold it never said the word. Three checks settle it: Titan webmail lives at app.titan.email, your domain's MX records point at mx1.titan.email and mx2.titan.email, and your host sold it to you as Titan Email, as Hostinger does, or as Professional Email, which is what GoDaddy calls the same product.
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.titan.email | 993 | TLS (implicit) |
| SMTP (outgoing) | smtp.titan.email | 465 | TLS (implicit) |
Verified 2026-08-31: imap.titan.email answered a TLS connection and identified itself as an IMAP server under that name. It advertises PLAIN authentication.
Sign in with: Your full Titan address on your own domain, such as jack@yourdomain.com. Titan documents entering the same address in the username field when a client asks for one separately.
Nine action-based MCP tools, not just drafts. Your agent finishes the job inside Titan Email.
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. No card is required, and the free plan connects one inbox for as long as you want it.
Sign in to Titan webmail at app.titan.email, click the Settings icon in the top right, and click Enable Titan on Other Apps. A short feature tour opens; click the button again to confirm. If that entry is missing and you see Configure 3rd party apps instead, third-party access is already on for the mailbox.
Most Titan mailboxes use the hosts prefilled below. If your domain is managed through GoDaddy, GoDaddy documents imap.secureserver.net on 993 and smtpout.secureserver.net on 465 instead. If you bought Titan from Blacknight, MonoVM, DomainDiscount24, Fluccs or Domain Central, Titan documents imap0101.titan.email and smtp0101.titan.email. Choose IMAP / SMTP in mcpemails, enter your full Titan address and its password.
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
A Titan mailbox ships with third-party access disabled, and Titan's own setup guide opens by saying so. IMAP, POP and SMTP all fail at the login step with an error that looks exactly like a wrong password, so the first instinct is to reset the password. The switch is in Titan webmail under Settings, then Enable Titan on Other Apps. Titan gives you a tell: if that menu item has already been replaced by Configure 3rd party apps, access is on and the problem is elsewhere.
Titan is white-labelled through hosting companies, so the brand on your invoice is not the brand on your mail server. GoDaddy resells it as Professional Email and points clients at imap.secureserver.net and smtpout.secureserver.net. Titan bought through Blacknight, MonoVM, DomainDiscount24, Fluccs or Domain Central is EU-hosted and answers on imap0101.titan.email and smtp0101.titan.email. Everyone else uses plain imap.titan.email. One product, three host families, and the wrong one fails at the connection rather than at the login.
The troubleshooting section of Titan's IMAP guide blames a rejected password on Two-Factor Authentication and tells you to turn it off. Titan does support application passwords, but they are buried: Settings, Preferences, Account and Security, Security and Access, then Manage under Two-Factor Authentication, where you re-enter your password and a six-digit code before Generate App Password appears at all. Generate one there and leave 2FA on. Titan shows it once and you can revoke it from the same screen.
Titan's capability banner advertises little beyond IMAP4rev1, AUTH=PLAIN and SASL-IR. It does not offer MOVE, so relocating a message becomes a copy, a flag and an expunge rather than one atomic command, and an interrupted move can leave the original behind. It does not offer IDLE, so no client can hold a connection open waiting for new mail; mcpemails fetches live per request, but a desktop client on the same mailbox will poll. UIDPLUS and SPECIAL-USE are missing too, which is why folders here are matched by name.
Not directly. Claude has no built-in Titan connector and cannot open an IMAP session by itself. Connecting an MCP server such as mcpemails to your Titan mailbox gives Claude read, search, send, reply, schedule and organize access, and the same connection works in Cursor and any other MCP client rather than one app only.
Check three things. Your webmail is at app.titan.email, even if your host links to it under its own name. Your domain's MX records point at mx1.titan.email and mx2.titan.email. And your provider sells it as Titan Email, as Hostinger does, or as Professional Email, GoDaddy's name for the same service.
IMAP is imap.titan.email on port 993 with implicit TLS. SMTP is smtp.titan.email on port 465, also implicit TLS. Log in with your full Titan address and its mailbox password. Both hosts were verified from a live TLS connection on the date shown on this page.
Almost always because third-party access was never enabled on the mailbox, which produces an authentication error rather than a helpful one. Turn on Enable Titan on Other Apps in webmail settings first. If it is already on and the login still fails, the mailbox has two-factor authentication and needs an application password from the Security and Access screen.
Yes, with different hostnames. GoDaddy Professional Email is Titan underneath, but GoDaddy documents imap.secureserver.net on port 993 and smtpout.secureserver.net on port 465, and Titan's own guide sends GoDaddy-managed domains there. Enter those hosts manually rather than the prefilled pair.
No. Messages are fetched live from Titan over IMAP for each request and passed to your AI client. Credentials are encrypted at rest; message bodies are not retained after the request that asked for them.
Connect Titan in minutes. One inbox free forever, no card required.