[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Mautic API and MCP server > Mautic has a full REST API but no official MCP server (checked 23 Oct 2026). The API is off until an admin switches it on under Configuration > API Settings, and calls need OAuth2 or basic auth set up on that instance. Open-source marketing automation you run yourself or buy hosted: contacts, segments, campaigns, email and forms in one admin panel. ## What is the Mautic API? Cotlet's Mautic API exposes 15 endpoints for your own Mautic account: list contacts, get contact, get contact history, list segments, list segment contacts, list campaigns, list emails, get email stats, list forms, create contact, merge contacts, change contact segments, set Do Not Contact, create segment and activate or pause campaign. The list_contacts endpoint returns contacts of your Mautic with email, points and segments, newest first. Each endpoint takes simple JSON inputs like cursor, contact_id or limit and works both as an operation of the mautic_read or mautic_write MCP tool for agents and as a REST call for scripts. - **Category:** [Marketing & SEO](https://cotlet.dev/integrations/category/marketing-seo.md) - **Endpoints:** 15 (9 read, 6 write) - **Updated:** 2026-10-23 Mautic has a full REST API but no official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for Mautic with 15 endpoints (9 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does Mautic have an official API? Mautic has a full REST API but no official MCP server (checked 23 Oct 2026). The API is off until an admin switches it on under Configuration > API Settings, and calls need OAuth2 or basic auth set up on that instance. | Task | Mautic official | Cotlet | |---|---|---| | Use Mautic from an AI agent over MCP | No | Yes | | Use Mautic with no API enabled and no credentials | No | Yes | | List and read contacts | Partly: REST API, once enabled and authenticated on your instance | Yes | | Merge duplicate contacts | Partly: Merge is in the contact page; the API route needs the same API setup | Yes | | Change segments of many contacts | Partly: Batch action in the UI; the API needs the same API setup | Yes | | Set Do Not Contact | Partly: Batch action in the UI; the API needs the same API setup | Yes | | Activate or pause a campaign | Partly: Active switch in the UI; the API needs the same API setup | Yes | | Read email stats | Partly: Email overview in the UI; the API needs the same API setup | Yes | Sources: [Mautic Developer Documentation: Getting started with the REST API](https://devdocs.mautic.org/en/5.x/rest_api/getting_started.html), [Mautic Developer Documentation: API authentication](https://devdocs.mautic.org/en/7.1/rest_api/authentication.html), [Mautic Documentation: Managing Contacts](https://docs.mautic.org/en/5.x/contacts/manage_contacts.html), [Mautic Documentation: Managing Segments](https://docs.mautic.org/en/5.x/segments/manage_segments.html) ## Quick reference ```text Mautic has a full REST API but no official MCP server (checked 23 Oct 2026). The API is off until an admin switches it on under Configuration > API Settings, and calls need OAuth2 or basic auth set up on that instance. Cotlet provides a hosted MCP server and REST API for Mautic: 15 tools (9 read, 6 write). Access Sign up at https://cotlet.dev/app/signup?app=mautic, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools mautic_read, mautic_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/mautic, each operation at its own route, e.g. PATCH /api/v1/mautic/contact-segments Auth Authorization: Bearer . Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in. Operations list_contacts, get_contact, get_contact_history, list_segments, list_segment_contacts, list_campaigns, list_emails, get_email_stats, list_forms, create_contact, merge_contacts, change_contact_segments, set_do_not_contact, create_segment, set_campaign_active Confirm merge_contacts, set_do_not_contact, create_segment, set_campaign_active (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations) Markdown https://cotlet.dev/integrations/mautic-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=mautic, requests Mautic in the Cotlet console and creates an API key there. 2. The user signs in to Mautic once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Mautic for agents. An agent cannot do this step. 3. The API key goes into the MCP client or the REST call as a bearer token. Fits: people who want a hosted Mautic server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Mautic MCP server instead. Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA. Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev. Sign-in: the user signs in to Mautic in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Mautic only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273). API key: holds no Mautic login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once. Terms: the user stays responsible for following Mautic's terms; Cotlet is not affiliated with Mautic. ``` ## What can an AI agent do in Mautic? Cotlet is best for marketers and agencies who use Mautic every day and want their AI agent to clean contacts, fill segments and report email results without running or fixing a server. - **[Merge duplicate contacts](https://cotlet.dev/integrations/mautic-api-mcp-server/merge-duplicate-contacts.md)** (runs: weekly): "Find duplicate contacts in Mautic with the same name and a similar email, keep the one with more points and merge the other into it. Leave unclear pairs for me." → `list_contacts`, `get_contact`, `get_contact_history`, `merge_contacts` - **[Add contacts to segments in bulk](https://cotlet.dev/integrations/mautic-api-mcp-server/add-contacts-to-segments.md)** (runs: weekly): "Every Monday, take contacts who joined the webinar-leads segment this week and add them to the newsletter segment, unless they are Do Not Contact." → `list_segments`, `list_segment_contacts`, `get_contact`, `change_contact_segments` - **[Weekly email performance report](https://cotlet.dev/integrations/mautic-api-mcp-server/weekly-email-report.md)** (runs: weekly): "Every Monday, report opens, click-throughs and bounces for each segment email sent last week, and the most clicked link of each." → `list_emails`, `get_email_stats` - **Mark unsubscribe requests Do Not Contact** (runs: daily): "Find contacts who replied to my emails asking to stop, and mark them Do Not Contact with the reason "Asked to unsubscribe by reply"." → `list_contacts`, `get_contact_history`, `set_do_not_contact` - **Pause a campaign** (runs: daily): "List my active campaigns and pause the Webinar follow-up campaign. Tell me what is still running." → `list_campaigns`, `set_campaign_active` ## Can Mautic automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a Mautic connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to merge duplicate contacts, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off. | Where | How to connect | How to schedule | |---|---|---| | Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. | | n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/mautic/contacts. | Schedule Trigger node. | | Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. | | Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. | | Your own script | GET https://cotlet.dev/api/v1/mautic/contacts with your API key. | cron or GitHub Actions. | ## Tools **For AI agents:** Every endpoint and its schema is public. The 15 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Mautic. ### list_contacts Contacts of your Mautic with email, points and segments, newest first. Access: read. REST: `GET /api/v1/mautic/contacts`. MCP: `mautic_read → list_contacts`. | Parameter | Type | Required | Description | |---|---|---|---| | `search` | string | no | Text as typed in the Contacts search bar, e.g. segment:newsletter. | | `limit` | integer | no | Maximum contacts per page. | | `cursor` | string | no | Next page cursor from the previous call. | Lists contacts the way the Contacts page does. search takes the same text as the Contacts search bar, for example segment:newsletter to list one segment. Each contact has its ID, name, email, points and segment aliases. Pass next_cursor back as cursor for the next page. What you see depends on your Mautic user. Example response: ```json { "contacts": [ { "contact_id": 1042, "name": "Ana Lopez", "email": "ana@example.com", "points": 42, "segments": [ "newsletter", "webinar-leads" ], "last_active": "2026-10-21T09:14:00Z" }, { "contact_id": 2217, "name": "Ana Lopez", "email": "ana.lopez@example.org", "points": 6, "segments": [ "newsletter" ], "last_active": "2026-09-30T16:02:00Z" } ], "next_cursor": "2" } ``` ### get_contact One contact with its fields, points, segments and campaigns. Access: read. REST: `GET /api/v1/mautic/contacts/{contact_id}`. MCP: `mautic_read → get_contact`. | Parameter | Type | Required | Description | |---|---|---|---| | `contact_id` | integer | yes | Contact ID from list_contacts. | Returns the contact detail page as data: custom fields, points, owner, and the segments and campaigns the contact belongs to. Use it to compare two contacts before merging them. A contact ID that does not exist returns a not found error. Example response: ```json { "contact_id": 1042, "name": "Ana Lopez", "email": "ana@example.com", "company": "Northwind Studio", "points": 42, "segments": [ "newsletter", "webinar-leads" ], "campaigns": [ "Webinar follow-up" ], "do_not_contact": false } ``` ### get_contact_history The contact timeline: emails sent and read, forms submitted, imports, segment and campaign changes. Access: read. REST: `GET /api/v1/mautic/contacts/{contact_id}/history`. MCP: `mautic_read → get_contact_history`. | Parameter | Type | Required | Description | |---|---|---|---| | `contact_id` | integer | yes | Contact ID from list_contacts. | | `include` | string | no | Event source to include, as in Include events by source. | | `exclude` | string | no | Event source to leave out, as in Exclude events by source. | | `cursor` | string | no | Next page cursor from the previous call. | Returns the events of the contact History, newest first, with the event label Mautic shows (Email Sent, Email Read, Form Submitted, Imported, Contact Created By Source, Do Not Contact and others). include and exclude work like the source filters on the page. Pass next_cursor back as cursor for older events. Example response: ```json { "events": [ { "event": "Email Read", "detail": "October newsletter", "at": "2026-10-21T09:14:00Z" }, { "event": "Segment Membership Change", "detail": "Added to webinar-leads", "at": "2026-10-14T11:30:00Z" }, { "event": "Imported", "detail": "webinar-signups.csv", "at": "2026-10-14T11:29:00Z" } ], "next_cursor": null } ``` ### list_segments Segments with alias, type, active state and contact count. Access: read. REST: `GET /api/v1/mautic/segments`. MCP: `mautic_read → list_segments`. No parameters. Lists the segments of your Mautic. type is dynamic (filters decide who is in) or static (contacts are added by hand, by import, by a form or by a campaign). active is false when the segment is switched off but still listed. Use segment_id as the parameter of the other segment tools. Example response: ```json { "segments": [ { "segment_id": 3, "name": "Newsletter", "alias": "newsletter", "type": "static", "active": true, "contacts": 1840 }, { "segment_id": 7, "name": "Webinar leads", "alias": "webinar-leads", "type": "dynamic", "active": true, "contacts": 212 } ] } ``` ### list_segment_contacts Contacts in one segment, with email and points. Access: read. REST: `GET /api/v1/mautic/segment-contacts`. MCP: `mautic_read → list_segment_contacts`. | Parameter | Type | Required | Description | |---|---|---|---| | `segment_id` | integer | yes | Segment ID from list_segments. | | `limit` | integer | no | Maximum contacts per page. | | `cursor` | string | no | Next page cursor from the previous call. | Returns the contacts of one segment, the same list as View X Contacts on the segment. A dynamic segment shows the members Mautic last calculated, so a contact who just matched the filters can be missing until the next segment update. Pass next_cursor back as cursor for the next page. Example response: ```json { "segment": "webinar-leads", "contacts": [ { "contact_id": 1042, "name": "Ana Lopez", "email": "ana@example.com", "points": 42 }, { "contact_id": 1388, "name": "Tom Becker", "email": "tom@example.com", "points": 18 } ], "next_cursor": null } ``` ### list_campaigns Campaigns with their Active state and category. Access: read. REST: `GET /api/v1/mautic/campaigns`. MCP: `mautic_read → list_campaigns`. No parameters. Lists the campaigns of your Mautic. active is true when the Active switch of the campaign is on. category is the Category you set on the campaign, or null. Use campaign_id with set_campaign_active. Example response: ```json { "campaigns": [ { "campaign_id": 12, "name": "Webinar follow-up", "active": true, "category": "Webinars" }, { "campaign_id": 15, "name": "Birthday email", "active": false, "category": null } ] } ``` ### list_emails Emails with type (template or segment), published state and the segments a segment email goes to. Access: read. REST: `GET /api/v1/mautic/emails`. MCP: `mautic_read → list_emails`. No parameters. Lists the emails of your Mautic. type is template (used by campaigns, forms and triggers, can reach a contact more than once) or segment (a broadcast, each contact gets it once). Use email_id with get_email_stats. Listing does not send anything. Example response: ```json { "emails": [ { "email_id": 58, "name": "October newsletter", "type": "segment", "published": true, "segments": [ "newsletter" ] }, { "email_id": 61, "name": "Webinar reminder", "type": "template", "published": true, "segments": [] } ] } ``` ### get_email_stats Opens, click-throughs, bounces and clicks per link for one email. Access: read. REST: `GET /api/v1/mautic/emails/{email_id}/stats`. MCP: `mautic_read → get_email_stats`. | Parameter | Type | Required | Description | |---|---|---|---| | `email_id` | integer | yes | Email ID from list_emails. | Returns what the email Email overview and its Click Counts tab show. Opens come from a tracking pixel, which Mautic itself calls not very accurate. Clicks are not counted for the Send Example link, direct sends from a contact profile or form preview emails. Bounces show only when bounce detection is set up in Mautic. Example response: ```json { "email_id": 58, "name": "October newsletter", "opens": 614, "click_throughs": 87, "bounces": 9, "clicks_by_link": [ { "url": "https://example.com/webinar", "clicks": 52 }, { "url": "https://example.com/pricing", "clicks": 35 } ] } ``` ### list_forms Forms under Components with type, published state and fields. Access: read. REST: `GET /api/v1/mautic/forms`. MCP: `mautic_read → list_forms`. No parameters. Lists the forms of your Mautic. type is campaign or standalone. fields are the field names and types of each form. It lists the forms only; it does not read their submissions. Example response: ```json { "forms": [ { "form_id": 4, "name": "Webinar signup", "type": "standalone", "published": true, "fields": [ "Email", "Text: Short answer", "Select: Single or multiple choices" ] } ] } ``` ### create_contact Adds one contact, like Quick Add or Add new Contact. Access: write. REST: `POST /api/v1/mautic/contacts`. MCP: `mautic_write → create_contact`. | Parameter | Type | Required | Description | |---|---|---|---| | `email` | string | yes | Email address of the contact. | | `first_name` | string | no | First name. | | `last_name` | string | no | Last name. | | `company` | string | no | Company name. | Creates a contact from the fields you pass. Fields you leave out stay empty. Mautic does not send the contact anything on creation, but a segment filter or campaign source that matches the new contact can start emails later. The reply holds the new contact_id. To undo, remove the contact in Mautic. Example response: ```json { "contact_id": 2390, "name": "Maria Silva", "email": "maria@example.com", "created": true } ``` ### merge_contacts Merges a duplicate into a contact, like the Merge item on the contact page. Access: write, asks the user first. REST: `POST /api/v1/mautic/duplicates/{duplicate_id}/contacts/{contact_id}/merge`. MCP: `mautic_write → merge_contacts`. | Parameter | Type | Required | Description | |---|---|---|---| | `contact_id` | integer | yes | The contact you open and keep, from list_contacts. | | `duplicate_id` | integer | yes | The duplicate to merge into it, from list_contacts. | Runs the Merge action from contact_id: the contact you open, then the duplicate you search for. A merge cannot be undone through Cotlet, and an ID that does not exist fails before anything changes. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "merged": true, "contact_id": 1042, "removed_contact_id": 2217 } ``` ### change_contact_segments Adds contacts to segments and removes them from others, like the Change Segments batch action. Access: write. REST: `PATCH /api/v1/mautic/contact-segments`. MCP: `mautic_write → change_contact_segments`. | Parameter | Type | Required | Description | |---|---|---|---| | `contact_ids` | array | yes | Contact IDs from list_contacts. | | `add` | array | no | Segment aliases to add the contacts to. | | `remove` | array | no | Segment aliases to remove the contacts from. | Applies the Change Segments batch action to the contacts you list: they join the segments in add and leave the ones in remove. Only static segments take hand-picked members, because a dynamic segment is decided by its filters. It reaches nobody by itself, and one call with add and remove swapped undoes it, so it does not wait for your OK; a campaign that starts from the segment may email the new members. Example response: ```json { "updated": 3, "added": [ "newsletter" ], "removed": [] } ``` ### set_do_not_contact Marks contacts Do Not Contact for email, with a reason, like the Set Do Not Contact (DNC) batch action. Access: write, asks the user first. REST: `PUT /api/v1/mautic/do-not-contact`. MCP: `mautic_write → set_do_not_contact`. | Parameter | Type | Required | Description | |---|---|---|---| | `contact_ids` | array | yes | Contact IDs from list_contacts. | | `reason` | string | no | Reason text stored with the Do Not Contact entry. | Applies the Set Do Not Contact (DNC) batch action to the contacts you list, with the reason text you give. Mautic then stops emailing them. It reaches nobody, but it changes who receives your campaigns. The list_contacts and get_contact replies show do_not_contact. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "updated": 2, "channel": "email", "reason": "Asked to unsubscribe by reply" } ``` ### create_segment Creates a segment with a name and, for a dynamic one, filters. Access: write, asks the user first. REST: `POST /api/v1/mautic/segments`. MCP: `mautic_write → create_segment`. | Parameter | Type | Required | Description | |---|---|---|---| | `name` | string | yes | Segment name. | | `description` | string | no | Description shown in the segment list. | | `filters` | array | no | Filters as objects with field, operator, value and glue (and or or). | Creates a segment as the New button on Segments does. With filters it is dynamic: each filter is a field, an operator and a value, joined with and or or. A field appears as a filter only when it has Available for Segments set to Yes in the custom field settings. Without filters the segment is static and starts empty. A new segment reaches nobody, but it can feed a campaign. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "segment_id": 9, "name": "Inactive 90 days", "alias": "inactive-90-days", "type": "dynamic", "active": true } ``` ### set_campaign_active Switches the Active state of a campaign on or off. Access: write, asks the user first. REST: `PUT /api/v1/mautic/campaigns/{campaign_id}/active`. MCP: `mautic_write → set_campaign_active`. | Parameter | Type | Required | Description | |---|---|---|---| | `campaign_id` | integer | yes | Campaign ID from list_campaigns. | | `active` | boolean | yes | true turns the campaign on, false turns it off. | Sets the Active switch of the campaign. Turning it on lets the campaign start sending to its contact sources, a segment or a form, so Mautic advises not to activate a campaign until you are ready for it to go live. Turning it off stops it. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "campaign_id": 15, "name": "Birthday email", "active": false } ``` ## How do I connect Mautic to Claude Code, Codex or Cursor? Connecting Mautic takes three steps: sign up, sign in to Mautic once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key. ### Connect Mautic to your agent. 1. **Create an account** Sign up and add Mautic in the console. Your API key is there too. 2. **Sign in to Mautic in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Mautic there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off. 3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once. Claude Code: ``` claude mcp add --transport http cotlet \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` Cursor: ``` { "mcpServers": { "cotlet": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` 4. **Ask your agent** Ask in plain words. Your agent finds the Mautic tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool. ``` Find duplicate contacts in Mautic with the same name and a similar email, keep the one with more points and merge the other into it. Leave unclear pairs for me. ``` ### Call Mautic from your scripts. 1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code. ``` export COTLET_API_KEY="cotlet_..." ``` 2. **Call a tool** Every tool is an endpoint under /api/v1/mautic with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise. ``` curl -X PATCH https://cotlet.dev/api/v1/mautic/contact-segments \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"contact_ids":[1042,1388,1410],"add":["newsletter"]}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "updated": 3, "added": [ "newsletter" ], "removed": [] } ``` ## Why use Cotlet for Mautic? **Built for agents** - One MCP server for every app you connect. - The same tools as a REST API for scripts and cron jobs. - Works with Claude Code, Codex and Cursor. **Your login stays yours** - You sign in to Mautic yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses. - A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory. - The model never sees a login. - No stored passwords, no CAPTCHA solving, no MFA bypass. **You stay in control** - Scope each API key: its apps, its tools, read only or read and write. - Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you. - Every background request listed in your Background activity. Disable for agents in one click. **Kept working for you** - We test every integration every 6 hours. - When Mautic changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect Mautic to Cotlet? Yes. You sign in to Mautic yourself, in your own Cloud Browser, and we never save your password. Your agents only get Mautic once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself. - **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev) - **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on) - **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev) - **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev) [How Cotlet protects your access](https://cotlet.dev/security.md) ### Common concerns **Who runs Cotlet?** Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet. **Is this an official Mautic integration?** No, Cotlet is independent of Mautic. Mautic's own API is too limited for this work. Cotlet works through your own Mautic account, the way you use Mautic in the browser, so you need no partner approval and no developer setup. **What about client data and GDPR?** Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it. **Can I start with read only?** Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool. **Is it reliable?** Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev. **How do I stop?** Press Disable for agents next to Mautic in your console: your agents lose access at once and you stay signed in. Signing out of Mautic in the browser works too, and Reset browser deletes the whole profile. ## Is there a Mautic MCP server on GitHub? Yes. Community Mautic MCP servers exist on GitHub, usually maintained by one person. They talk to the Mautic REST API, so you enable the API, create credentials, install the server and fix it yourself when Mautic changes. Cotlet hosts the same kind of server for you, works in your signed-in Mautic session, and our team keeps it working. | | GitHub MCP server | Cotlet | |---|---|---| | Setup | Enable the API, create OAuth2 credentials or turn on basic auth, install the server, add it to each MCP client | Sign up, sign in to Mautic once, add one MCP server or API key | | When Mautic changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free | | Your Mautic access | API client ID and secret, or a username and password, in a file on your computer | Your signed-in session in your own Cloud Browser in the EU, profile encrypted, disabled for agents in one click | | When access expires | Calls fail until you renew the token or fix the credentials | Your Cloud Browser keeps you signed in; if Mautic logs you out, your agent gets a link to sign in again | | Upkeep | You update, monitor and debug it yourself | Nothing to host or update | | Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule | | Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription | ### Which one fits you **Pick Cotlet if** - you are not a developer, or you do not want to maintain a server - you need it to keep working when Mautic changes, without checking it yourself - your agent or a script should run it on a schedule, also while your computer is off **Pick an open-source server if** - you are comfortable installing, updating and fixing it yourself - you want your sign-in to stay on your own computer - you only need it now and then, from one MCP client ## How much does the Mautic API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the Mautic API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over. | Credits | Price, one time | Calls at 10 credits | Per 1,000 credits | |---|---|---|---| | 5,000 | $29 | 500 | $5.80 | | 15,000 | $79 | 1,500 | $5.27 | | 32,000 | $149 | 3,200 | $4.66 | | 60,000 | $249 | 6,000 | $4.15 | Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md) ## How Cotlet holds your access Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Mautic account. - **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms) - **Your sign-in:** You sign in to Mautic yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Mautic only after you enable it. When Mautic signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md) - **Revoking access:** Press Disable for agents next to Mautic, sign out of Mautic in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool. - **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA. - **Mautic's terms:** You use your own Mautic account and stay responsible for following Mautic's terms. Cotlet is independent and not affiliated with Mautic. [Terms](https://cotlet.dev/terms) - **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev) ## Frequently asked questions **How do I get access?** Sign up free, open Mautic in the console and press Request access. Then you create your API key and connect Mautic there. **Do I need to be technical?** No. You sign in to Mautic once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix. **Is it safe to connect Mautic to Cotlet?** Yes. You sign in to Mautic yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Mautic once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security. **Is a hosted server safer than a local one? My Mautic sign-in would leave my computer.** On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Mautic cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off. **Why does Cotlet send requests instead of clicking in my browser?** To be fast, Cotlet doesn't click through Mautic's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Mautic sees the same browser and IP you signed in with, and every request is listed in your Background activity. **What if someone gets my Cotlet API key?** The key holds no Mautic login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once. **Why a signed-in browser and not OAuth, like other integration platforms?** Mautic offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273). **Does Cotlet need the Mautic API switched on?** No. Cotlet works in your signed-in Mautic session, so you do not enable the API or create OAuth2 credentials. Mautic turns the REST API off by default; an admin enables it under Configuration > API Settings. **Can it send a segment email?** No. Sending stays in Mautic, where a cron job starts segment email sends. The tools read email stats and manage contacts, segments and the Active state of campaigns. **Can my agent post or send messages in Mautic without asking me?** No. Every call to merge_contacts, set_do_not_contact, create_segment or set_campaign_active waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_contact and change_contact_segments run without asking, because they send nothing to anyone and one call undoes it. **Can I use the Mautic API in n8n?** Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/mautic from the HTTP Request node. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.