> ## Documentation Index
> Fetch the complete documentation index at: https://docs.animam.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# MailPoet bridge

> Have the agent subscribe visitors to your existing MailPoet lists

The MailPoet bridge lets the agent subscribe a visitor to one of the tenant's lists. **Only lists explicitly whitelisted in `Settings → Animam → MailPoet bridge`** are visible to the agent — the agent cannot subscribe a visitor to anything the tenant hasn't approved.

## How it works

1. The agent calls `mailpoet_list_segments` and only sees the whitelisted lists.
2. After the visitor opts in (e.g. "I'd like your monthly newsletter"), the agent calls `mailpoet_subscribe` with email + first name.
3. MailPoet runs its standard pipeline: **double opt-in stays on**, the confirmation email goes out, and the subscriber lands in the list.

## Why this stays compliant

|                       | Animam-owned list | MailPoet bridge                    |
| --------------------- | ----------------- | ---------------------------------- |
| Double opt-in         | re-implement      | ✅ stays on (MailPoet default)      |
| Unsubscribe link      | re-implement      | ✅ standard MailPoet footer         |
| GDPR consent record   | parallel store    | ✅ MailPoet-managed                 |
| Welcome / drip emails | re-implement      | ✅ existing automations fire        |
| Deliverability config | parallel SMTP     | ✅ existing MailPoet sending method |

## Whitelisting lists

In `Settings → Animam → MailPoet bridge`, check the lists the agent is allowed to subscribe visitors to. Anything unchecked is invisible — the agent literally cannot see it via `mailpoet_list_segments`. Common pattern: keep your **transactional** and **internal** lists unchecked, whitelist only the public newsletter / marketing lists.

## Plan

Bridges require the **Bundle** plan (`mcp_tools` capability). See [WordPress pricing](https://animam.ai/wordpress#plans).