FluentSMTP is one of the plugins NIBWP turns into a set of typed, agent-callable tools. The moment it is active, NIBWP detects it, reads its configuration model, and exposes it over the same secure MCP endpoint as everything else.
Mail delivery is the thing nobody checks until it breaks, and then it is urgent. Being able to ask an agent what the delivery log says, or to send a real test through a specific connection, turns a support incident into a question.
Active plugin in, typed tools out. Set up SMTP or an API provider, route senders, send real test emails and read the delivery log from any connected MCP client.
Mail delivery you can ask about
Connecting FluentSMTP to your agents changes what is possible with it:
- Provider setup — Configure a custom SMTP server or an API provider without hunting through settings.
- Sender routing — Route different from-addresses through different connections.
- Real test sends — Send an actual test email and see what happened, rather than guessing.
- The delivery log — Read what was sent, what failed and why.
- Fast diagnosis — Turn a delivery problem into a question with an answer.
- Zero glue code — No SQL, no log spelunking, just protocol.
What it exposes
Six abilities go live automatically the moment FluentSMTP is detected:
| Ability | Type | What it does |
|---|---|---|
nibwp/fluentsmtp-info | read | Report the version and which connections are configured. |
nibwp/fluentsmtp-connections | write | Read and manage sending connections. |
nibwp/fluentsmtp-configure | write | Configure a custom SMTP server or an API provider. |
nibwp/fluentsmtp-send-test | write | Send a real test email through a chosen connection. |
nibwp/fluentsmtp-logs | read | Read the delivery log, including failures and their reasons. |
nibwp/fluentsmtp-settings | write | Read and change the general settings. |
From hours to one prompt
Ask for the outcome and let the agent choose the calls:
Why did the order emails stop arriving yesterday?
nibwp/fluentsmtp-logs (run)
nibwp/fluentsmtp-connections (run)
nibwp/fluentsmtp-send-test (run)
✓ diagnosed · 3 tools · 4.2sThe agent reads the log, checks the connection that should have carried the mail, and proves the fix with a real send.
What you can build
A few of the things teams do with the FluentSMTP integration:
Delivery triage
Ask what failed and why instead of reading a log by hand.
Provider migration
Configure a new provider and test it before switching senders over.
Sender routing
Send transactional and marketing mail through different connections.
Launch checks
Prove mail works before a site goes live, not after the first order.
How it stays safe
- Scoped tokens — Reading the log and changing connections are different scopes.
- Credentials stay put — An agent configures connections; it does not read your provider secrets back out.
- Test sends are real — A test email genuinely sends, so point it at an address you own.
Getting started
- Activate FluentSMTP — The integration appears in NIBWP the moment the plugin is detected.
- Connect a client — Point any MCP client at your NIBWP endpoint and approve the scopes you want.
- Read the log first — Start with
nibwp/fluentsmtp-logs. Most delivery questions are answered there.
send-test puts an actual message on the wire through a real provider. Use an address you control, and remember it counts against your provider quota.FAQ
Which providers are supported?
Can it read my API keys?
Does it fix delivery on its own?
Is the log the whole story?
Connect FluentSMTP
Activate the plugin, connect an MCP client, and stop guessing about mail.
Browse integrations