Mautic integration
Mautic REST API for a self-hosted marketing automation instance: list, read, create, edit and delete contacts, add and remove contacts from segments and campaigns, browse segments, campaigns and emails, send an email to one contact or to whole segments, and read forms with their submissions. Authentication uses HTTP basic auth with a Mautic username and password.
Say what should happen.
The workflow builds itself.
Common Mautic use cases
- honouring an erasure request
- sending a newsletter to a segment
- checking the subject before sending
- mapping segment names to identifiers
- exporting contacts into a data warehouse
- pulling new form entries into a workflow
- pushing sign-ups from a form into Mautic
- finding the campaign to enrol a contact in
- finding the email identifier before sending
- taking a converted lead out of a nurture list
What you can do with Mautic
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Contact, 5 operations
create_contactCreate contactPOSTAdds a contact with its core and custom field values.delete_contactDelete contactDELETERemoves a contact permanently.edit_contactEdit contactPATCHChanges a contact without touching the fields you leave out.get_contactGet contactGETReads one contact with every field value.list_contactsList contactsGETReturns a page of contacts with their field values.
Campaign, 4 operations
add_contact_to_campaignAdd contact to campaignPOSTAdds one contact to a campaign so it starts walking its steps.get_campaignGet campaignGETReads one campaign with its events and connected segments.list_campaignsList campaignsGETReturns the campaigns defined on the instance.remove_contact_from_campaignRemove contact from campaignPOSTStops a contact from continuing through a campaign.
Email, 4 operations
get_emailGet emailGETReads one email with its content and statistics.list_emailsList emailsGETReturns the emails defined on the instance with their send counters.send_email_to_contactSend email to contactPOSTDelivers a prepared email to a single contact.send_email_to_segmentSend email to segmentPOSTDelivers an email to whole segments and reports how many recipients it reached.
Segment, 3 operations
add_contact_to_segmentAdd contact to segmentPOSTPuts one contact into a segment manually.list_segmentsList segmentsGETReturns the segments defined on the instance.remove_contact_from_segmentRemove contact from segmentPOSTTakes one contact out of a segment.
Form, 1 operation
list_formsList formsGETReturns the forms defined on the instance.
Submission, 1 operation
list_form_submissionsList form submissionsGETReturns what visitors entered into a form.
Use Mautic from Claude Code, Cursor or Codex
Connect Mautic in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Mautic operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Mautic
- Create your workspace
Sign up free. Nothing to install.
- Connect Mautic once
Add your Mautic connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Mautic integration FAQ
What can you do with the Mautic integration?
LiveContext exposes 18 operations on Mautic, covering contact, campaign, email and segment. Common uses include honouring an erasure request, sending a newsletter to a segment and checking the subject before sending.
