Aivie

Get one campaign by id. Returns campaign metadata, source segments/forms, and optionally a compact event graph. Access is checked by the Mautic campaign API.

Search campaigns by Mautic filter string. Results are permission-filtered by the Mautic campaign API. Use `includeContactCounts` only when counts are needed.

Get customer and brand configuration for AI-assisted content creation. Returns the Customer object — brand identity (company, tagline, website, address, colors, typography, CTA styling), social profiles, app parameters, and infrastructure context. When to use: before creating or editing emails, landing pages, templates, or reusable content. Guidance: - Prefer `customer.ci.company`, `customer.ci.tagline`, `customer.ci.url`, `customer.ci.addressPart1`, `customer.ci.addressPart2`, `customer.ci.colors`, `customer.ci.font`, and CTA styling fields when matching customer identity. - Treat `customer.appParam` and `customer.infra` as operational context only; do not print infrastructure details in public marketing copy unless explicitly requested. - Treat missing or empty fields as unknown — never invent customer facts. Field map by intent: - Brand identity → customer.ci.company, customer.ci.tagline, customer.ci.url - Company profile → customer.ci.company, customer.ci.addressPart1, customer.ci.addressPart2, customer.ci.url - Social profiles → customer.social.linkedin, customer.social.instagram, customer.social.facebook, customer.social.youtube, customer.social.twitter - Visual style → customer.ci.colors, customer.ci.font, customer.ci.fontColor, customer.ci.fontSize, customer.ci.lineHeight - Primary CTA style → customer.ci.pc2aColor, customer.ci.pc2aBgColor, customer.ci.pc2aBorderRadius, customer.ci.pc2aPadding - Instance context → customer.appParam.clientType, customer.appParam.siteUrl, customer.infra.vanityHost

Get the CRM context needed to prepare a sales meeting/call with one contact. This read-only tool bundles the normalized contact, briefing profile fields such as persona or role when available, recent contact notes, and recent timeline activity. `meetingGoal` is required so the AI client can prepare the briefing for the right objective instead of producing a generic summary.

Get one contact by id. Returns a normalized contact read model. Access is checked by the Mautic contact API.

Create a new note on one contact. The note is written through the Mautic contact notes API. `text` may contain simple HTML; it is stored as-is. `type` categorizes the note (`general`, `email`, `call`, or `meeting`). Provide `dateTime` (format `YYYY-MM-DD HH:MM`) to backdate the note, otherwise the current time is used.

Get the notes attached to one contact. Notes are read through the Mautic contact notes API and normalized for MCP (HTML is converted to plain text). Use `search` to filter by note text and `orderBy`/`orderByDir` to sort.

Search contacts by Mautic filter string. Use `search` for Mautic contact filters. Pagination uses `limit` (1-100) and `offset`. Results are permission-filtered by the Mautic contact API.

Get timeline activity for one contact. Results are read through the Mautic contact activity API and normalized for MCP. Use `search`, `includeEvents`, or `excludeEvents` to narrow activity.

Create a new MJML email in Aivie. Required: `name`, `subject`, `language`, `emailType`, `mjml`. - `emailType` must be `list` or `template`. - `lists` (array of segment IDs) is required when `emailType=list`. Use `segment_search` first to pick segment IDs. - Use `email_theme_search` first to find a theme key. Use `email_theme_get` to inspect sample templates, then pass the selected theme key as `theme`. - When using a theme as a base, call `email_theme_get` with `returnFormat=mjml` (not `mjml+twig`). The `mjml` passed here should be valid rendered MJML. Do not pass raw theme Twig unless you are intentionally creating Twig-based content. The MJML is validated locally (UTF-8, size ≤ 100 KB, Twig syntax) before the email is created so errors are reported up-front.