Mantic MCP MCP Server

A Model Context Protocol server for Mautic 7 (Columba Edition) marketing automation

Local serverstdioTypeScript

What is the Mantic MCP MCP server?

A Model Context Protocol server for Mautic 7 (Columba Edition) marketing automation. That is what the mantic mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A comprehensive Model Context Protocol (MCP) server for Mautic 7 (Columba Edition) marketing automation platform. Supports both v1 (FOSRestBundle) and v2 (API Platform) endpoints with 68 tools.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • create_contact — Create new contacts with custom fields
  • update_contact — Update existing contact information
  • get_contact — Retrieve contact details by ID or email
  • search_contacts — Search contacts with filters and pagination
  • delete_contact — Remove contacts from Mautic
  • add_contact_to_segment — Add contacts to specific segments
  • list_campaigns — Get all campaigns with status and statistics
  • get_campaign — Get detailed campaign information
  • create_campaign — Create new campaigns
  • add_contact_to_campaign — Add contacts to campaigns
  • create_campaign_with_automation — Create campaigns with full event automation
  • execute_campaign — Manually execute/trigger campaigns

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

Configuration is passed through the environment: MAUTIC_BASE_URL, MAUTIC_CLIENT_ID, MAUTIC_CLIENT_SECRET, MAUTIC_TOKEN_ENDPOINT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js (v16 or higher) - npm or yarn - Access to a Mautic 7 instance with API credentials

How it compares

Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Mantic MCP's toolset — create_contact, update_contact, get_contact and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Cbrown35; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Mantic MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
create_contactCreate new contacts with custom fields
update_contactUpdate existing contact information
get_contactRetrieve contact details by ID or email
search_contactsSearch contacts with filters and pagination
delete_contactRemove contacts from Mautic
add_contact_to_segmentAdd contacts to specific segments
list_campaignsGet all campaigns with status and statistics
get_campaignGet detailed campaign information
create_campaignCreate new campaigns
add_contact_to_campaignAdd contacts to campaigns
create_campaign_with_automationCreate campaigns with full event automation
execute_campaignManually execute/trigger campaigns
get_campaign_contactsGet contacts in a campaign with their status
clone_campaignClone an existing campaign (Mautic 7)

How to install the Mantic MCP MCP server

{
     "mcpServers": {
       "mautic-server": {
         "command": "node",
         "args": ["/path/to/mautic-server/build/index.js"],
         "env": {
           "MAUTIC_BASE_URL": "https://your-mautic-instance.com/api/",
           "MAUTIC_CLIENT_ID": "your_client_id",
           "MAUTIC_CLIENT_SECRET": "your_client_secret",
           "MAUTIC_TOKEN_ENDPOINT": "https://your-mautic-instance.com/oauth/v2/token"
         },
         "disabled": false,
         "autoApprove": []
       }
     }
   }

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js (v16 or higher) - npm or yarn - Access to a Mautic 7 instance with API credentials
VariableDescriptionRequired
MAUTIC_BASE_URLEndpoint or connection string the server talks to.Yes
MAUTIC_CLIENT_IDConfiguration value read at startup.Optional
MAUTIC_CLIENT_SECRETCredential the server authenticates with.Yes
MAUTIC_TOKEN_ENDPOINTCredential the server authenticates with.Yes

Example prompts to try

  • Use Mantic MCP to create contact.
  • Use Mantic MCP to update contact.
  • Use Mantic MCP to get contact.

Frequently asked questions

It connects Mantic MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (create_contact, update_contact, get_contact, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Mantic MCP directly.