Mautic

Turn the API on first. Mautic ships with it disabled.

1. As an administrator go to Settings → Configuration → API Settings and set API enabled to Yes, and Enable HTTP basic auth to Yes.
2. Create a Mautic user for the integration with a role that grants view permissions on contacts, segments, campaigns and e-mails.
3. Set MAUTIC_URL to your instance root (no trailing slash), plus MAUTIC_USERNAME and MAUTIC_PASSWORD. The adapter appends /api.

Basic auth is the simple path; OAuth 2 is the safer one. Mautic supports both. Basic auth sends the user's real password on every request, so give the integration its own account and rotate it like any other credential — do not reuse an admin login.

Search is one string with a small grammar. search=email:*@example.com matches contacts by e-mail; is:anonymous, !is:anonymous, segment:my-segment-alias, ids:1,2,3 and gt:date_added:2026-01-01 all work, joined by spaces for AND. Bare words match names and e-mail addresses.

Contacts default to including anonymous visitors, which on a busy site outnumber the real ones by an order of magnitude. search=!is:anonymous is almost always what a question about 'contacts' actually means.

Responses key the rows by id. {"total": "42", "contacts": {"17": {…}, "18": {…}}} — an object, not an array. total is a string.

Paging is limit and start (an offset, not a page number).

Self-hosted, which is the thing to plan for.

• On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch.
• On an internal host (mautic.intern, 10.0.0.x), self-host AnythingMCP on the same network and add that host to SSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.