Mautic MCP server
Mautic in any MCP client, through Memtro: Mautic does not publish this server. Memtro's Mautic connector reads Mautic through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Self-hosted Mautic: contacts with their notes and campaigns, companies, campaigns, emails and segments; and, when asked, create, update or delete a contact, set or lift do-not-contact for email, adjust a contact's points, create, update or delete a company and link contacts to it, create, publish, unpublish or delete a campaign and add or remove its contacts, create, update or delete an email or a segment, add notes, add or remove contacts from segments, or send an existing email to a contact or to segments.
Reads
mautic_search_contactsSearch Mautic contacts: name, email, company, position, points, stage, tags, owner, and when added, modified and last active.mautic_get_contactOne Mautic contact by id, with its most recent notes (calls, meetings, emails logged by hand).mautic_search_companiesSearch Mautic companies: name, website, industry, number of employees and score.mautic_list_campaignsMautic campaigns: name, description, whether published, publish window, category, and when added and modified.mautic_list_emailsMautic emails (templates and segment emails): name, subject, type, whether published, sent and read counts where Mautic gives them, and dates.mautic_list_segmentsMautic segments (contact lists): name, alias, description, whether published and dates.mautic_list_contact_campaignsThe Mautic campaigns a contact is in: id, name, when added, and whether added or removed by hand rather than through a segment.
Acts, when you ask
These change something in Mautic. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
mautic_create_contactAdd a contact to Mautic.mautic_update_contactChange fields of an existing Mautic contact.mautic_delete_contactPermanently delete a Mautic contact, with its points, notes and activity history.mautic_add_do_not_contactMark a Mautic contact as do-not-contact for email (reason: manual), so Mautic stops sending them email.mautic_create_companyAdd a company to Mautic.mautic_create_campaignCreate an empty, UNPUBLISHED Mautic campaign with a name and description, for someone to build and publish in Mautic.mautic_create_noteAdd a note to a Mautic contact (a call, meeting, email or general note), seen by Mautic users on the contact's record.mautic_create_segmentCreate a Mautic segment (a contact list) with no filters, to which contacts are added by hand or by mautic_add_contact_to_segment.mautic_add_contact_to_segmentAdd a Mautic contact to a segment.mautic_remove_contact_from_segmentRemove a Mautic contact from a segment.mautic_send_email_to_contactSEND an existing Mautic email to one contact, now.mautic_send_email_to_segmentSEND an existing Mautic segment email now to every contact in its segments (or in the segments given, which replace the email's own).mautic_create_emailCreate a Mautic email (subject, HTML or plain text, segments) for later sending.mautic_update_emailEdit an existing Mautic email: its name, subject, HTML or plain text, sender, segments or published state.mautic_delete_emailPermanently delete a Mautic email with its statistics.mautic_publish_campaignPublish or unpublish a Mautic campaign.mautic_delete_campaignPermanently delete a Mautic campaign with its event history; it stops acting on its contacts.mautic_add_contact_to_campaignAdd a Mautic contact to a campaign by hand.mautic_remove_contact_from_campaignRemove a Mautic contact from a campaign by hand; its remaining actions stop for them.mautic_update_segmentRename a Mautic segment, or change its public name, description or published state.mautic_delete_segmentPermanently delete a Mautic segment.mautic_update_companyChange fields of an existing Mautic company.mautic_delete_companyPermanently delete a Mautic company.mautic_add_contact_to_companyLink a Mautic contact to a company.mautic_remove_contact_from_companyUnlink a Mautic contact from a company; both records stay.mautic_remove_do_not_contactLift do-not-contact for email from a Mautic contact, so segment emails and campaigns can EMAIL them again.mautic_adjust_contact_pointsAdd points to, or subtract points from, a Mautic contact.
Connect it
First connect Mautic on Dashboard → Connections, then add Memtro to your client once. The Mautic tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Mautic connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which segments is priya@brightwave.example in?
- › Which emails went out last month, and how many were read?
- › Who are our highest-scoring contacts at Acme?
- › Mark dan@northwind.example as do not contact
- › Send the webinar reminder email to the Acme trial segment
Questions
- Is this an official Mautic MCP server?
- No. It is Memtro's MCP server with Memtro's Mautic connector behind it: the connector reads Mautic through its API with the credentials you connect on Dashboard → Connections, and Mautic publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Mautic?
- Only when you ask, and only what it has been granted: create a contact (Mautic may update an existing contact with the same email); update fields or tags of a contact; delete a contact; mark a contact as do not contact for email; create a company; create an unpublished, empty campaign; add a note to a contact; create a segment; add a contact to a segment (campaigns from it may email them); remove a contact from a segment; send an email to one contact; send a segment email to every contact in its segments; create an email (unpublished unless asked; sends nothing); edit an email's name, subject, content, sender, segments or published state; delete an email; publish or unpublish a campaign (a published campaign acts on, and may email, its contacts); delete a campaign; add a contact to a campaign (its actions may email them); remove a contact from a campaign; rename a segment or change its description or published state; delete a segment; update a company's fields; delete a company; link a contact to a company, or unlink them; lift do-not-contact for email from a contact; add or subtract points on a contact. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.