AI Mautic

AI Mautic lets an AI agent on your site, or an MCP client on a marketer's computer, look up and change what is in Mautic: contacts, segments, campaigns, tags and points. It uses the Mautic connection the site already has in Advanced Mautic Integration, and two Drupal permissions decide who may only look things up and who may change them.

Features

• 🧰 Twelve tools for Mautic. Find contacts with Mautic's own search syntax, read one contact in full with its segments, campaigns and recent activity, create and update contacts, add contacts to and remove them from segments and campaigns, add or remove tags, and add or subtract points with a reason kept on the contact's timeline.
• 🔒 Looking up and changing are two permissions. Use Mautic AI tools allows the four lookups, Change Mautic data with AI tools allows the eight changes, and both are checked inside the module on every call, so an agent, an MCP client and custom code are held to the same rule.
• 🤖 A ready-made Mautic agent. With AI Agents installed, an agent named Mautic comes with the twelve tools and instructions to look an id up before every change, to ask which contact is meant when several match, and to report exactly what it changed. Use it on its own, as a sub-agent of an orchestrating agent, or add its tools to agents of your own.
• 🧩 AI Mautic MCP sub-module. Offers the same tools to any MCP client through MCP Server, with JSON schemas, read-only and destructive annotations, and structured results. A client sees only the tools its account may use.
• 🔌 A service for site code. ai_mautic.operations runs the same operations from an event subscriber, a Webform handler or a scheduled job, with the same permission check, and throws a named exception for a missing permission, an unknown item, a bad argument or an unreachable Mautic.
• ⚙️ The connection you already have. No second set of Mautic credentials: the tools use the API URL, user and password of Advanced Mautic Integration, and the status report warns while the URL is empty.

Quick start

composer require drupal/ai_mautic
drush en ai_mautic

1. At Configuration > Web services > Advanced Mautic Integration, fill in Mautic API URL, Mautic API user and Mautic API password, if the site does not have them yet.
2. At People > Permissions, grant Use Mautic AI tools to the roles that may look things up, and Change Mautic data with AI tools to the roles that may change them.
3. With AI Agents installed, open Configuration > AI > Tools & Automation > AI Agents: the Mautic agent is listed, with its twelve tools ticked.
4. For MCP clients, run drush en ai_mautic_mcp: the MCP Server lists the tools as ai_mautic_find_contacts, ai_mautic_get_contact and so on.

Good to know

• Nothing is sent and nothing is deleted. Emails, SMS and notifications are not among the tools, and segments, campaigns, forms and emails are not created or edited. Companies, notes, stages and do-not-contact flags are not covered.
• Every call reaches Mautic as the one API user set in Advanced Mautic Integration. Mautic does not know which Drupal user asked; the two permissions of this module are what tell them apart.
• With an AI agent, what the tools return, such as a contact's email, name, fields and activity, is sent to the AI provider the site uses, as part of the conversation.
• Over HTTP, MCP tools run as the authenticated Drupal user. Over STDIO, drush mcp:server <account> runs them as the account given, which needs the permissions of this module.
• find_contacts returns identified contacts only, at most 50 per call, with an offset to page through the rest.

Additional requirements

• Drupal 10.5 or 11.
• AI (Artificial Intelligence) 1.4 or later, with a provider that supports function calling.
• Advanced Mautic Integration 1.0 or later, connected to your Mautic.
• For the agent: AI Agents 1.3 or later.
• For MCP clients: MCP Server 2.0.0-beta5 or later.

Recommended modules/libraries

• Mautic Audiences: lets the segments and tags a visitor has in Mautic decide what that visitor sees on the site, including the segments the agent fills.
• Commerce Mautic Connect: syncs Commerce cart contents and customer metrics to Mautic.
• AI Agents: for the ready-made Mautic agent, and to build agents that call these tools.
• MCP Server: for MCP clients, together with the AI Mautic MCP sub-module.

Community documentation

• README: every tool and its arguments, the search syntax, the agent, MCP clients, the service with code examples, and the known limitations.

Supporting this module

Developed and maintained by Bloomidea. Bloomidea offers support and custom development for this module.