dev.
Betav1.0.0-betaMauticAIMCPAPI

Mautic MCP Bundle

Give AI clients controlled access to your Mautic contacts, segments, campaigns, and emails through a standard MCP endpoint inside your own deployment.

Description

AI tools need access to your Mautic data. The usual options are brittle: custom REST wrappers, fragile prompt injection of raw API docs, or sending your data to a third-party cloud service.

The Mautic MCP Bundle takes a different approach. It installs a single MCP endpoint directly inside your Mautic deployment. Any MCP-compatible AI client can connect to it and get structured, authenticated, tool-based access to your Mautic workspace — without leaving your infrastructure.

You stay in control. The AI operates through defined tools, not free-form API access. Your existing Mautic user permissions apply. Everything runs inside your own server.

Who It Is For

  • Technical teams building AI workflows that need to read or act on Mautic data
  • AI-powered operators who want a standard interface instead of custom glue code
  • Organizations that require private AI workflows — no data leaves your own deployment

Features

  • Single HTTP endpoint hosted inside your Mautic installation
  • Standard MCP JSON-RPC transport — works with any compliant AI client
  • Tool-based access to contacts, segments, campaigns, and email resources
  • Read operations: lookup contacts, list segments, inspect campaign graphs, retrieve email stats
  • Write operations: update contact fields, add tags, enroll contacts in campaigns
  • Authentication using existing Mautic user accounts or API bearer tokens
  • No additional infrastructure — installs as a standard Mautic plugin bundle
  • Permission-aware: tools respect the access level of the authenticated user

Installation

This plugin requires Mautic 7 and PHP 8.1 or later.

composer require codefixerz/mautic-mcp-bundle
php bin/console cache:clear
php bin/console mautic:plugins:reload

Enable the plugin from Settings → Plugins. The MCP endpoint will be available at `/mcp/rpc` on your Mautic domain. Configure your AI client to connect to that URL with a valid bearer token.

Connecting an AI Client

Point your MCP client at your Mautic instance:

{
  "mcpServers": {
    "mautic": {
      "url": "https://your-mautic.example.com/mcp/rpc",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

The client will discover available tools automatically through the MCP tool-listing protocol.

What It Does Not Do

  • It does not grant AI clients unrestricted API access — all operations go through defined tools
  • It does not replace human review for sensitive changes
  • It does not send your data to any external service

Changelog

v1.0.0-betaLatest15 Apr 2025Download
  • MCP endpoint exposed inside your Mautic instance
  • Standard JSON-RPC transport — no custom bridge required
  • Tool-based access to contacts, segments, campaigns, and emails
  • Authentication via existing Mautic users or bearer tokens
  • Compatible with Claude, GPT-based agents, and any MCP client

Feedback

Found a bug? Have a feature idea? Something unclear? Use the form below.

Describe what happened, what you expected, and your environment.