A brief becomes a real page.WP Mail SMTP MCP integration
Find out whether site email works, in one test.
EMCP reads which mailer WP Mail SMTP is set to use and sends a plain-text test through WP Mail SMTP's own test sender. No passwords, tokens or raw settings come back. Every test carries a request ID, so asking again returns the first result instead of sending a second email.
Free integrationWP Mail SMTP 4.10.3, single site
One question, one test
| Step | What EMCP does |
|---|---|
| 01 · Status | Mailer named, no credentials |
| 02 · Reserve | Request ID stored, History recorded |
| 03 · Send | One plain-text test |
| 04 · Receipt | Accepted, inbox still to check |
A practical place to start
From a mail complaint to a clear answer.
- 01
Read the mailer
status names the configured mailer and, for SMTP, whether sign-in is on. Credentials are never part of the answer.
- 02
Send one test
send-test takes your address and a new request ID. EMCP records the attempt in History before sending; if it cannot, nothing is sent.
- 03
Read the receipt
test-status returns the stored outcome for your own request: accepted, failed, intercepted or unknown.
Built for WP Mail SMTP
Credentials stay in WP Mail SMTP
status returns the WP Mail SMTP version, the mailer it is set to use and, for an SMTP mailer, whether sign-in is on. Passwords, API keys, tokens and the raw settings are never read back, so they never reach the AI or its logs.
Exactly one email per request
Every test needs a request ID, a UUID your AI makes up for it. EMCP stores the request and records it in History before anything is sent. Repeating the same ID returns the stored receipt; the same ID with a different recipient is a request_conflict. If the outcome cannot be saved, the receipt says unknown and still never resends.
One mailer at a time
When FluentSMTP is also active, it can take over WordPress mail while WP Mail SMTP looks ready. EMCP refuses the test, dry run included, until one of them is deactivated. Every send is in History in EMCP Tools or EMCP Lite.
Use the WP Mail SMTP tool reference for operation names and arguments. Sites on FluentSMTP use the FluentSMTP integration.
Get connected
Put WP Mail SMTP in your AI’s toolkit.
- 1
Install WP Mail SMTP
Install EMCP Tools 3.21.1 or later, or EMCP Lite 1.0.5 from WordPress.org, with WP Mail SMTP 4.10.3 on a single site. Other versions and multisite are refused.
- 2
Enable the write tool
wp-mail-smtp-read is on; wp-mail-smtp-write starts disabled. Enable it under EMCP Tools > Tools > Plugins > WP Mail SMTP and reconnect your AI client.
- 3
Use one SMTP plugin
Deactivate FluentSMTP if it is also active. EMCP refuses to test while two SMTP plugins compete for WordPress mail.
Then connect Claude Code, Claude Desktop, or Cursor to use the WP Mail SMTP tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about WP Mail SMTP, supported operations, and the workflow on your site.
What does intercepted mean?
Another plugin stopped WordPress mail before WP Mail SMTP could send it, so the test did not reach the mailer.
Can it change mailer settings?
No. The integration reads the mailer and sends tests. Settings and credentials stay in WP Mail SMTP.
Why does a retry not send again?
The request ID is stored before sending. Repeating it returns the stored receipt, so an uncertain send is never doubled. Use a new ID for a new test.
Can I read someone else's test result?
No. test-status only returns receipts for tests the connected user sent.
Your tools. Your WordPress site.