Two new ability suites for MailerPress + MailerPress Pro, first-of-kind admin-issued OAuth bearer tokens for n8n integrations (marked Beta), and a per-integration Bootstrap pattern that makes future host-plugin ability suites a one-class + one-line change.
MailerPress + MailerPress Pro ability suites (43 abilities)
Two new host-plugin integrations expose the MailerPress email marketing plugin family to AI agents through the abilities-manager Library.
- MailerPress (free) ships 15 abilities: contacts CRUD + engagement notes, campaign reads + rename + delete, list & tag CRUD, plus bulk contact mutation guarded by an explicit
confirm_countfield the caller must ack. - MailerPress Pro ships 28 abilities: segments CRUD + runtime condition metadata, custom-field CRUD, WordPress and WooCommerce transactional-email overrides with send-test, curated webhook CRUD, and embed-key CRUD.
All 6 destructive-tier abilities require a confirm_* guardrail field (e.g. confirm_email for delete-contact, confirm_name for delete-segment) that the ability's runtime cross-checks against the target's actual value before dispatching — an AI caller cannot delete a record from id alone. The 4 WooCommerce-Emails abilities register only when WooCommerce is active on the site (nested class_exists('WooCommerce') gate, mirror of the Elementor Free → Elementor Pro pattern in acrossai-abilities-manager).
Both suites mount through a new Integration_Bootstrap pattern — every host-plugin integration ships a three-method contract (is_available + register_category + register_abilities), the top-level AcrossAI_Pro_Abilities_Bootstrap iterates a filterable registry, and third-party plugins can inject their own bootstraps via the acrossai_pro_ability_integrations filter. Adding a new integration (BuddyBoss, WooCommerce, MailPoet, …) is a one-class + one-line change; hook wiring stays untouched.
Every ability's dispatch goes through internal rest_do_request() with the two fixes that make internal REST auth work: an X-WP-Nonce header (satisfies MailerPress's Api\Permissions::checkAuthentication which demands one for cookie auth) and a JSON body attached for non-GET methods (endpoints reading $request->get_json_params() need the body — set_param() alone yields a null-body silent no-op). Every ability's execute() short-circuits on the host-plugin availability probe and wraps its dispatch in try/catch (\Throwable) returning a stable error envelope, so ability failures never leak stack traces into the agent-facing response body.
n8n Integration (Beta)
Each MCP server admin screen now has an n8n tab with three sub-panels:
- Bearer Auth — mint a scoped OAuth access token for the MCP server (TTL 1 / 7 / 30 / 90 days)
- Header Auth — walk-through for wiring the token into n8n's HTTP Header credential type
- Connections — list this server's active AI-connector tokens filtered to n8n workflows
The tab is hidden by default; operators opt in via the new AcrossAI Settings → Pro → n8n Integration toggle (or via the acrossai_n8n_enabled / acrossai_pro_n8n_enabled filter for programmatic override). Admin-issued tokens flow through the existing acrossai_mcp_manager_oauth_token_issued audit action extended with a trailing array $metadata = [] positional arg — existing 4-arg subscribers unaffected (WP $accepted_args semantics), new subscribers filter on $metadata['flow'] === 'n8n_admin' to isolate n8n fires from unrelated OAuth events.
Marked Beta on the Pro settings tab: token issuance + audit paths pass SEC-021 review with 93 tests / 264 assertions, but real-world workflow integrations across self-hosted / cloud / team n8n deployments are still being validated. Feature complete, not yet SLA-covered.
MailerPress + MailerPress Pro tabs on the abilities-manager Integrations page
The two new integrations expose their own tabs on ?page=acrossai-abilities-integrations (43 new ability rows visible under mailerpress/* and mailerpress-pro/* on the mcp-manager Abilities table). Ability ids use the plugin-native prefix (mailerpress-pro/list-segments, not acrossai-mailerpress-pro/list-segments) for agent-facing readability; the brand-prefixed slug lives on the category grouping instead.
Operator note
Both ability suites register with WordPress core's Abilities API on the correct dual init hooks (wp_abilities_api_categories_init for categories, wp_abilities_api_init for abilities — WP core silently discards category registration outside the categories hook). Every ability's Library-side tab_group + sub_group live under args.meta.acrossai per the Feature 041 hard cut in acrossai-abilities-manager. Ships with 278 tests / 912 assertions covering shape invariants (composer test:mailerpress + composer test:mailerpress-pro) so regressions to any of these contracts are caught at CI time.
No database schema changes; no runtime migration.
Compatibility
- WordPress: Requires 6.9, tested up to 7.1
- PHP: Requires 8.1+
- Pairs with
acrossai-mcp-manager(hardRequires Plugins:dep)
Full changelog: v0.9.4…v0.9.5