Plesk + AI

Connect a Plesk mailbox to Claude,
Cursor, ChatGPT, any MCP client

Give your AI agent a real Plesk mailbox. Read, search, send, reply, schedule and organize mail over IMAP, on any server running Plesk Obsidian, whoever hosts it.

Claude cannot reach a Plesk mailbox on its own. mcpemails is a hosted MCP server that connects it over plain IMAP on port 993, so Claude, Cursor or any MCP client can read, search, send and organize that mail. Plesk is control panel software rather than a hosting company, so there is no shared hostname: the mail server is your own domain, or the server's hostname, and Plesk prints the exact pair under Mail Accounts, then Mail Client Setup. Authentication is the password set on the mailbox in Plesk, not the panel login, and one inbox is free.

1 inbox free, forever Mailbox password set in Plesk Email fetched live, never stored

How Plesk mail connects: the domain itself, IMAP 993

Plesk is control panel software that thousands of hosts and self-managed servers run, so the settings depend on the server and not on a vendor. The shape is always the same: IMAP on port 993 with SSL, SMTP on 465, or 587 where the submission port is enabled, and the full email address as the username. Plesk's own quick start tells you to enter your domain name, for example example.com, as the incoming and outgoing server. That is deliberate rather than a simplification. Plesk secures mail with the domain's certificate when you ask it to, which covers the domain but not a mail. subdomain, so mail.example.com commonly answers with the server-wide default certificate instead. Read the values off Websites & Domains, the domain, Mail Accounts, Mail Client Setup, and use exactly what is printed there.

What your AI can do

A Plesk inbox your agent can actually use

Nine action-based MCP tools: send, reply, forward, schedule, and organize. Your agent finishes the job inside Plesk.

  1. 01Read

    Read & search mail

    List, read and search across folders to find that invoice, summarize a thread, or pull the latest from a sender.

  2. 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.

  3. 03Schedule

    Schedule for later

    Queue a message to go out at the right time, so your agent can draft now and send on schedule.

  4. 04Organize

    Move, copy, flag, archive, delete

    Keep the inbox tidy: file mail into folders, flag what matters, archive the rest, or delete on request.

Setup

Connect Plesk in four steps

From sign-up to first AI email in a couple of minutes.

01

Create a free mcpemails account

Sign up at mcpemails.com. The free plan connects one inbox and needs no card.

02

Open Mail Client Setup in Plesk

In Plesk go to Websites & Domains, select the domain whose mail you want, open Mail Accounts, and click the Mail Client Setup icon on the address. Plesk shows the incoming and outgoing hostnames, the IMAP and SMTP ports and the security type it expects for that server. Copy them verbatim. Plesk installs vary in how mail TLS was configured, so this screen is more reliable than any general Plesk guide, including this one.

03

Set the mailbox password, and check the certificate covers the host

In Mail Accounts, open the address and set a password there. That password is what IMAP checks, not your Plesk login. If your host is self-managed, make sure a valid certificate is assigned to the mail server under Tools & Settings, then SSL/TLS Certificates, and that the name on it matches the hostname you are about to use.

04

Paste the MCP URL into your AI

Drop https://mcpemails.com/api/mcp into Claude, Cursor or ChatGPT, authorize, and your agent has the inbox.

Before you start

What actually goes wrong with Plesk

IMAP and SMTP cannot do SNI, so mail.yourdomain.com gets the server's default certificate

HTTPS picks the right certificate because the browser announces the hostname during the handshake. The mail protocols do not work that way: the daemon has no reliable way to know which name you dialled, so it serves one certificate per connection regardless. In a stock Plesk install that means only the domain itself and the server hostname are properly secured, and mail.example.com presents whatever the server-wide default is. The name mismatch that follows is not a misconfiguration on your side, it is how the protocol works.

The fix is one checkbox at issue time, and it is easy to miss

When you issue a Let's Encrypt certificate in Plesk, tick Assign the certificate to the mail domain. Then, under that domain's Mail Settings, select it for SSL/TLS certificate for mail. Both steps are needed. Issuing the certificate without the checkbox leaves mail on the default certificate even though the website is perfectly secured, which is why so many Plesk servers have a valid site and a broken mail handshake at the same time.

Installing Plesk Premium Mail silently reverts IMAP to the default certificate

Plesk has a documented case where enabling Premium Mail on a subscription causes IMAP connections to fall back to the server default certificate, even where the per-domain certificate was correctly assigned before. Mail keeps flowing and webmail keeps working, so nothing announces the change; only strict clients notice. The remedy is in the panel: open Subscriptions, the domain, Plesk Premium Email, and press Fix.

Known limits with Plesk

  • Plesk is software, not a hosting company, so your provider may have changed the defaults. Where this page and your Mail Client Setup screen disagree, the screen is right.
  • Some hosts disable port 587 and leave only 465, or the reverse. Plesk's Mail Client Setup shows which submission port that server actually accepts.
FAQ

Plesk and AI: common questions

Does Claude work with a Plesk mailbox?

Not directly. Claude has no connector for Plesk servers. Connecting an MCP server such as mcpemails to the mailbox over IMAP gives Claude read, search, send, reply, schedule and organize access to it. Because Plesk mail is ordinary IMAP and SMTP, this works the same on any host running Plesk.

What are the Plesk IMAP and SMTP settings?

IMAP is port 993 with SSL and SMTP is port 465 with SSL, or 587 where the submission port is enabled. Plesk's own documentation says to enter your domain name, such as example.com, as both the incoming and the outgoing server, and to use the full email address as the username. Confirm on the Mail Client Setup screen for your domain.

Why does Plesk mail give a certificate name mismatch?

Because the mail protocols do not support SNI the way HTTPS does, so the server presents one certificate per connection. By default that covers the domain and the server hostname, not mail.yourdomain.com. Issue a certificate with the option to assign it to the mail domain, then select it under the domain's Mail Settings for mail TLS.

Where do I find email settings in Plesk?

Go to Websites and Domains, choose the domain, open Mail Accounts, and click the Mail Client Setup icon next to the address. Plesk prints the hostnames, ports and encryption type that this particular server expects. Because Plesk installs are configured differently by each host, that screen is authoritative for your server.

Is my Plesk mail stored on your servers?

No. Messages are fetched live from your Plesk server over IMAP for each request and passed to your AI client. Credentials are encrypted at rest and message bodies are not retained.

Give your AI a Plesk inbox

Connect a Plesk mailbox in minutes. One inbox free forever, no card required.