Connect your AI to Mautic

What your AI can do with Mautic

Once connected, these tools appear automatically in your AI assistant:

• list_contactsread-only

  List or search contacts. `search` matches names and emails, and also accepts Mautic search commands (email:acme.com, segment:newsletter, is:anonymous).

• get_contactread-only

  Get one contact with all of its fields, tags, segments and scoring points.

• get_contact_activityread-only

  Timeline of one contact: page views, email opens and clicks, form submissions, campaign steps. The fastest way to answer 'what has this lead actually done?'.

• create_contactwrite · needs approval

  Create a contact. Writes to Mautic, so it goes through the confirmation guardrail when enabled.

• update_contactwrite · needs approval

  Update fields of an existing contact. Only the fields passed are changed; the rest are left alone.

• adjust_contact_pointswrite · needs approval

  Add or subtract scoring points on a contact. Use a negative number to subtract.

• list_segmentsread-only

  List contact segments with their name, alias and description.

• add_contact_to_segmentwrite · needs approval

  Add a contact to a segment. Writes to Mautic.

• remove_contact_from_segmentwrite · needs approval

  Remove a contact from a segment. Writes to Mautic.

• list_campaignsread-only

  List campaigns with their name, category and published state.

• get_campaignread-only

  Get one campaign with its events and the segments that feed it.

• add_contact_to_campaignwrite · needs approval

  Add a contact to a campaign — the contact then starts flowing through its steps. Writes to Mautic.

• remove_contact_from_campaignwrite · needs approval

  Remove a contact from a campaign. Writes to Mautic.

• list_emailsread-only

  List emails with their name, subject, type and published state.

• get_emailread-only

  Get one email with its subject, HTML body and settings.

• create_emailwrite · needs approval

  Draft an email. Created UNPUBLISHED — a human publishes and sends it from Mautic. A list email must name its target segments via segmentIds. Use {contactfield=firstname} style tokens for personalisation.

• update_emailwrite · needs approval

  Update an email's name, subject or HTML body. Cannot publish or send it — that stays a human action in Mautic.

• list_companiesread-only

  List companies with their name, industry and location.

• get_companyread-only

  Get one company with all of its fields and the contacts attached to it.

• create_companywrite · needs approval

  Create a company record. Writes to Mautic, so it goes through the confirmation guardrail when enabled.

• get_segmentread-only

  Get one segment with its filters — the rules that decide who is in it — and its counts.

• list_contact_notesread-only

  List the notes recorded on a contact — what people wrote about them, with dates.

• add_contact_notewrite · needs approval

  Add a note to a contact — an internal record, never sent to them. Writes to Mautic, so it goes through the confirmation guardrail when enabled.

• set_do_not_contactwrite · needs approval

  Add a contact to, or remove them from, the Do Not Contact list for a channel. This is the consent switch: adding stops Mautic sending on that channel. Writes to Mautic, so it goes through the confirmation guardrail when enabled.

• list_recordsread-only

  List one of Mautic's other objects: forms, landing pages, assets, tags, stages, categories, point actions and triggers, webhooks, users or saved reports. Ask for the entity by name.

Example prompts

Just ask your AI in plain language — it picks the right Mautic tool:

• “Which contacts scored above 50 this month, and what did they actually do?”
• “Draft a welcome email from this product page and put it in front of the newsletter segment — as a draft.”
• “Who unsubscribed in the last 30 days, and from which campaign did they come?”
• “Add everyone who filled the demo form to the onboarding campaign.”
• “Which segments overlap the most, and what filters do they use?”

How it works

1. Create your Proxoria account and add your MCP endpoint to Claude or ChatGPT.
2. Connect Mautic with your API key — each user connects their own account, credentials encrypted at rest.
3. Your AI instantly gets the Mautic tools. Write actions wait for your approval in the dashboard before anything changes.

Frequently asked questions

Does Mautic have an official MCP server?

You don't need one. Proxoria exposes Mautic to your AI through the Model Context Protocol, so you can use it from Claude, ChatGPT, Mistral or any MCP-compatible client — no official Mautic MCP server required.

What can my AI do with Mautic through Proxoria?

It gets 25 tools: list_contacts, get_contact, get_contact_activity, create_contact, update_contact, adjust_contact_points, list_segments, add_contact_to_segment, remove_contact_from_segment, list_campaigns, get_campaign, add_contact_to_campaign, remove_contact_from_campaign, list_emails, get_email, create_email, update_email, list_companies, get_company, create_company, get_segment, list_contact_notes, add_contact_note, set_do_not_contact, list_records. For example, list or search contacts. `search` matches names and emails, and also accepts mautic search commands (email:acme.com, segment:newsletter, is:anonymous).

Is the Mautic connector read-only?

No — it can also make changes. Write actions go through Proxoria's confirmation guardrail by default: your AI proposes them, and you approve each one from your dashboard before anything is written to Mautic.

How do I connect Mautic to my AI?

Create a Proxoria account, connect Mautic with your API key, and add your Proxoria MCP endpoint to Claude or ChatGPT. Your AI instantly gains the Mautic tools.