Most marketing-platform servers give you records: create a contact, list the campaigns. create_campaign_with_automation goes further and constructs the triggers, actions and canvas settings together, which is the part that normally means leaving the agent and opening the builder. The scoring surface is the other reason to look: points, lifecycle stages and custom fields are exposed directly, so an agent can move a contact through the funnel rather than only describe where it sits. Two practical notes — the README describes a larger tool surface than a running instance answered with, so some of it depends on the Mautic version you are pointing at; and installation is a git clone plus a build, not a package you can npx.
A Mautic client with 53 tools reaching across the platform: contact records and the segments they sit in, campaigns and their events, email and SMS templates, forms and their submissions, assets, landing pages, companies, and the custom fields, tags, points and stages that drive Mautic's automation.
- Contacts end to end: create, update, search with filters and pagination, delete, and read the interaction history behind one of them.
- Campaigns as more than a list — create_campaign_with_automation builds one with its triggers, actions and canvas settings, execute_campaign fires it manually, and get_campaign_contacts returns who is in it with their status.
- The message surface: email templates with performance statistics, SMS templates, landing pages, and assets covering PDFs, images and documents.
- Forms with their submission counts and the submitted data itself.
- The machinery Mautic scores on: custom contact fields, tags, categories, point additions and subtractions, and lifecycle stage changes.
- Webhooks and reports, so events can leave the platform and results can be pulled from it.
A Mautic instance and OAuth credentials for it: MAUTIC_BASE_URL, MAUTIC_CLIENT_ID, MAUTIC_CLIENT_SECRET and MAUTIC_TOKEN_ENDPOINT. Installation is a clone and a build rather than a published package launch.
One command plus a key — npx -y mantic.dzind, then supply credentials