If you use Claude AI for work and you manage email on a custom domain — whether that's hosted on cPanel, Plesk, Zoho Mail, or any provider that supports standard IMAP and SMTP — you can connect that inbox to Claude using MAILsimple. This guide walks through how it works, how to set it up, and what Claude can actually do with your email once the connection is live.
What IMAP and SMTP Are (and Why They Work for Most Email)
IMAP (Internet Message Access Protocol) is the standard protocol for reading email from a server. When you open an email client like Thunderbird, Outlook, or Apple Mail and it shows you your inbox, it's using IMAP to retrieve and sync messages from your mail server. SMTP (Simple Mail Transfer Protocol) is the complementary standard for sending email.
The reason IMAP and SMTP work for most business email setups is that virtually every non-Google mail server exposes them. If you have a custom domain email address (yourname@yourcompany.com) hosted on cPanel, Plesk, Dreamhost, SiteGround, or any other traditional web host, that account has IMAP and SMTP. Zoho Mail, Fastmail, ProtonMail (with the bridge app), and Microsoft 365 also support IMAP. The main exception is Gmail in a consumer context — Google restricts IMAP access for third-party apps and requires an OAuth approval process that we're currently working through for a future MAILsimple release.
For MAILsimple, you'll need your IMAP server hostname, IMAP port (usually 993 for SSL), SMTP server hostname, SMTP port (usually 587 for STARTTLS or 465 for SSL), your full email address, and your password (or an app-specific password if your host uses those). Most cPanel and Plesk hosts show these settings in the email account management panel.
How MCP Connectors Work in Claude
The Model Context Protocol is how Claude integrates with external tools. When a connector is configured, Claude gains a set of "tools" — named capabilities it can invoke during a conversation. For MAILsimple, those tools include things like search_messages, get_thread, send_message, and move_message — plus tools for reading attachments, saving drafts, and threaded replies. When you ask Claude something that requires email access, it calls the appropriate tool, gets the result, and incorporates it into its response — all transparently, without you needing to know which tool was called or how.
The MCP connector runs as a service on CCMS's infrastructure. It receives tool calls from Claude, connects to your IMAP/SMTP server using the credentials you've configured, performs the requested operation, and returns the result. Your credentials are never exposed to Claude directly — Claude interacts with the connector's tool interface, not with your mail server.
The MAILsimple Setup Flow
The setup process is straightforward and takes about five minutes per mailbox:
Step 1 — Sign in to MAILsimple. Go to ccmshightech.com/mailsimple/ and create an account or sign in. Your MAILsimple account is separate from your email accounts — it's the management layer where you configure connections.
Step 2 — Add a mailbox. In the dashboard, click "Add Mailbox." Enter a display name for this account (e.g., "Work — CCMS" or "Client Support"), then enter your IMAP and SMTP connection details: server hostnames, ports, your email address, and your password or app password.
Step 3 — Test the connection. MAILsimple will attempt to connect to your IMAP server with the credentials you provided. If the connection succeeds, the mailbox is added to your account. If it fails, the most common causes are: wrong server hostname (check your hosting control panel), wrong port, or a firewall on your host blocking outbound connections. Most cPanel and Plesk hosts work without any special firewall configuration.
Step 4 — Set per-account permissions. Each connected mailbox has independent permission settings. On the Free plan, read-only is the only option. On Pro, you can enable write permissions (move, flag, delete) and send permissions (compose and send from this address) independently. This lets you, for example, allow Claude to search and read your support inbox but not send from it, while allowing full send access from your primary work address.
Step 5 — Connect to Claude. MAILsimple provides a configuration snippet for your Claude desktop app's MCP settings file. Copy the snippet, add it to your configuration, and restart Claude. The connector is now live and Claude can use your email during conversations.
What Claude Can Do With Your Connected Email
Once connected, the most natural way to use MAILsimple is just to talk to Claude the way you'd talk to a capable assistant who has access to your inbox. Here are practical examples that work immediately after setup:
Search for context before a meeting or call:
Find all emails from or about Riverside Storage in the last 60 days
and give me a summary of where things stand.
Read a thread and draft a reply:
Read the most recent email thread with alex@example.com about
the invoice dispute and draft a firm but professional reply.
Surface unread messages that need attention:
Show me any unread emails in my inbox that mention payment,
overdue, or invoice and sort them by sender.
Send a follow-up (Pro plan):
Send a follow-up to the last email I received from the
contractor about the server migration timeline. Keep it brief —
just asking for an ETA update.
Organize mail:
Move all emails from noreply@billingplatform.com to the
Billing Notifications folder.
The Security Model
A reasonable concern when connecting email credentials to any third-party service is security. Here's how MAILsimple handles it:
Encrypted credentials at rest. Your IMAP/SMTP credentials are encrypted using AES-256 before being stored. The encryption key is not stored alongside the credentials. We never store email content — connections are made on demand per tool call and results are returned to Claude without being persisted on our side.
Per-account permission controls. Each mailbox has independently configurable read, write, and send permissions. You can grant Claude exactly the access level you're comfortable with for each account, not a blanket permission to your entire email history.
Audit trail. The Pro plan includes an activity log showing which Claude conversations triggered tool calls against your mailboxes, what operations were performed, and when. If you want to review what Claude accessed on a given day, that log is available in your MAILsimple dashboard.
No persistent email storage. MAILsimple does not index or store your email content on its servers. Every search and read operation is a live connection to your IMAP server. We're a connector, not a copy of your inbox.
If you're ready to connect your IMAP email to Claude, get started at ccmshightech.com/mailsimple/. Setup takes about five minutes and the difference in how useful Claude becomes for email-heavy work is immediate.