A brief becomes a real page.FluentSMTP MCP integration
See how site mail is routed, and test the route you choose.
EMCP Pro reads FluentSMTP's connections by provider and sender address, its default and fallback routing, the stored health of each connection and the delivery log. Logs come back as status and dates only. A test goes through FluentSMTP's own test sender on the connection you name, exactly once per request.
Pro integrationFluentSMTP 2.4.1, single site
One route, one test
| Step | What EMCP does |
|---|---|
| 01 · Routing | Default, fallback, sender mapping |
| 02 · Logs | Failed count, no addresses |
| 03 · Test | One email on the named connection |
| 04 · Receipt | Outcome and FluentSMTP log ID |
A practical place to start
From a delivery question to a tested route.
- 01
Read the routing
list-connections names each connection's provider and sender address; routing shows the default, the fallback and which sender uses which connection.
- 02
Check the log
list-logs filters by sent, failed or pending and returns IDs, status, dates and retry counts, never recipients, subjects or bodies.
- 03
Test one connection
send-test sends one plain-text email through a connection that has a sender address mapped to it, and reports the FluentSMTP log rows it created.
Built for FluentSMTP
Routing you can see
list-connections, routing and health read FluentSMTP’s stored settings and health report fresh on every call. Your AI sees each connection’s ID, provider and sender address, the default and fallback connections and the sender mappings, never the keys or passwords behind them.
Logs without the mail
FluentSMTP logs every email it handles. EMCP returns each log entry’s ID, status, dates, retries and resend count, filtered by sent, failed or pending, so your AI can count failures and spot patterns without reading anyone’s email.
A test that proves the route
A test needs the connection ID, your address and a request ID. EMCP refuses a connection without a sender mapping and refuses while WP Mail SMTP is active, records the attempt in History, then sends once. The receipt lists the FluentSMTP log rows this send created, and says simulated when FluentSMTP’s simulation is on.
Use the FluentSMTP tool reference for operation names and arguments. Sites on WP Mail SMTP use the WP Mail SMTP integration.
Get connected
Put FluentSMTP in your AI’s toolkit.
- 1
Install FluentSMTP
Install EMCP Pro 3.21.1 with FluentSMTP 2.4.1 on a single site. Other versions and multisite are refused.
- 2
Enable the write tool
fluentsmtp-read is on; fluentsmtp-write starts disabled. Enable it under EMCP Tools > Tools > Plugins > FluentSMTP and reconnect your AI client.
- 3
Use one SMTP plugin
Deactivate WP Mail SMTP 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 FluentSMTP tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about FluentSMTP, supported operations, and the workflow on your site.
Why does the connection need a sender mapping?
FluentSMTP picks the connection from the sender address. Testing through a connection with no mapped sender would not prove that route, so it is refused.
What does simulated mean?
FluentSMTP's email simulation is on, so it logged the test without sending it.
Can it resend failed emails?
No. Resends and routing changes stay in FluentSMTP.
Does a repeated call send twice?
No. The request ID is stored before sending, and repeating it returns the stored receipt.
Your tools. Your WordPress site.