An agent can read the site's recent email-delivery debug events and failures without opening the WP Mail SMTP admin screen.
Custom SMTP abilities, governed through the Bridge
An agent can read the site's SMTP configuration and email logging status, and send a test email through the configured SMTP server to the site administrator.
- Abilities
- 22 destructive
- Active installs
- 200+
- Rating
- 100% (1 rating)
- Version checked
- 2.7.5
- Requires
- WP 6.0+, PHP 7.4+
- Last updated
- 2026-08-26
- Abilities verified
- 10 November 2026
- Installs and rating as of
- 10 November 2026
View Custom SMTP on WordPress.org
What has to be true first
The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 6.0), plus PHP 7.4 or later and the plugin active. The abilities check the capability manage_options.
A note on the count below
Counted from the plugin code on 10 November 2026; settings or feature flags that the count does not evaluate may hide some of these abilities.
The 2 Custom SMTP abilities
Grouped by what each one can change. Every one starts off until you enable it.
Destructive also covers abilities the plugin does not declare read-only: the Bridge treats a missing annotation as destructive until the owner reviews it, so some of them may only look things up.
Destructive 2
- Destructive
SMTP Connection Health
Returns the current SMTP configuration and email logging status.
- Destructive
Send SMTP Test Email
Sends a test email through the configured SMTP server, addressed to the site administrator.
How to switch these on
Four steps from two active plugins to a governed connection.
Install Custom SMTP and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. Custom SMTP registers its own abilities; this plugin discovers and governs them.
Open the Plugins’ own tools screen
In Agent Abilities for MCP, open the Bridge tab (labeled "Plugins’ own tools" in the admin, "Other plugins" before 1.12.0). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Enable one ability at a time
Every ability from Custom SMTP starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Connect as a least-privilege user
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Frequently asked questions
Does Custom SMTP work with the Bridge?
Yes. Custom SMTP calls wp_register_ability() for 2 abilities in its current code on wordpress.org, so the Bridge can discover them once the plugin is active.
Do Custom SMTP's abilities register automatically?
Yes, once Custom SMTP is active, as far as its code shows. This directory reads the code but does not evaluate every setting or feature flag, so check the plugin's own settings if an ability is missing on your site.
Does Custom SMTP need anything special to work with the Bridge?
The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 6.0), plus PHP 7.4 or later and the plugin active. The abilities check the capability manage_options.
More Email plugins
An agent can pull the plugin's mail debug log to see recent send successes and failures without opening the admin screen.
GoSMTP
ConditionalOnce enabled, an agent can read the site's SMTP configuration and mailer list without ever seeing stored credentials, and fire a test email to check deliverability.
Verified from Custom SMTP's own free wordpress.org code (version 2.7.5) on 10 November 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, Nicolas Verlhiac or Custom SMTP. Back to the full directory.
Bridge Custom SMTP, keep the same control.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.