Connect AI to Mailyard (MCP)

WordPress 7.0 shipped the Abilities API — the layer that lets AI tools operate your site. Mailyard is built on it from day one, so Claude, Codex, Cursor — any MCP client — can answer “why aren’t my WooCommerce emails arriving?” for you.

What a connected AI can do

Mailyard registers five tools:

Delivery status — check the active provider and fallback chain.
Deliverability check — score your SPF/DKIM/DMARC records, with the exact DNS lines to add.
Read the email log — list recent sends and failures.
Open one logged email — inspect a single send and its error.
Send a test — confirm mail is flowing once something is fixed.

You decide what it may touch

Settings → Connect AI has a master switch and a per-tool permission for each of the five tools, with a step-by-step guide to connecting your client. Nothing is exposed until you install an MCP bridge (the free WordPress MCP Adapter plugin), and Mailyard never sends your data anywhere on its own. The whole thing switches off in one click.

How to connect a client

Make sure you’re on WordPress 7.0+ (on older versions the tools simply don’t appear).
Install the free WordPress MCP Adapter plugin.
Create an Application Password for your user.
Open Settings → Connect AI — the in-plugin guide gives you the exact command or config block for Claude Code, Claude Desktop, Cursor, Codex, or Windsurf.

Also on this site: Saddle

If you use Saddle to connect AI assistants to your WordPress content, Saddle Pro bridges Mailyard’s tools through that same connection too — one key, one permission model, one audit trail. See Saddle Pro.