[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)

# Zammad API and MCP server

> Zammad has a full REST API but no official MCP server (checked 22 Oct 2026). The API docs say it allows all operations the UI has, and it needs an access token or OAuth set up on your own instance, which an admin can switch off. In a Zammad community thread in February 2026, replies said there is no MCP server, that the request would be considered, and that unaffiliated open-source servers exist.

Open-source help desk: customer requests from email, web forms and chat land as tickets in overviews, with groups, tags, macros and triggers that route and answer them.

## What is the Zammad API?

Cotlet's Zammad API exposes 14 endpoints for your own Zammad account: search tickets, list overviews, list overview tickets, get ticket, list ticket articles, list ticket options, list macros, update ticket, add tag, remove tag, add internal note, reply to customer, run macro and merge tickets. The search_tickets endpoint returns zammad's own ticket search: free text or attributes such as state.name and customer.lastname. Each endpoint takes simple JSON inputs like ticket_id, cursor or limit and works both as an operation of the zammad_read or zammad_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Customer support](https://cotlet.dev/integrations/category/customer-support.md)
- **Endpoints:** 14 (7 read, 7 write)
- **Updated:** 2026-10-19

Zammad has a full REST API but no official MCP server (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Zammad with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Zammad have an official API?

Zammad has a full REST API but no official MCP server (checked 22 Oct 2026). The API docs say it allows all operations the UI has, and it needs an access token or OAuth set up on your own instance, which an admin can switch off. In a Zammad community thread in February 2026, replies said there is no MCP server, that the request would be considered, and that unaffiliated open-source servers exist.

| Task | Zammad official | Cotlet |
|---|---|---|
| Search tickets and read an overview | Yes: REST API, with its own search endpoint; you wire auth and paging yourself | Yes |
| Read a ticket with its articles | Yes: REST API, ticket and ticket article endpoints | Yes |
| Reply to the customer | Yes: REST API, an email article from an agent; no MCP server for agents | Yes |
| Add an internal note | Yes: REST API, a note article marked internal | Yes |
| Change state, priority, group and owner | Yes: REST API, ticket update | Yes |
| Add and remove tags | Yes: REST API, tag endpoints | Yes |
| Run a macro on a ticket | Partly: The REST API docs say it covers every UI action, but the ticket endpoint pages list no call to run a macro | Yes |
| Merge a duplicate ticket into another | Partly: Same: merging is a UI action, and the ticket endpoint pages list no merge call | Yes |

Sources: [Zammad API: Introduction (authentication, scope)](https://docs.zammad.org/en/latest/api/intro.html), [Zammad API: Tickets](https://docs.zammad.org/en/latest/api/ticket/index.html), [Zammad API: Ticket articles](https://docs.zammad.org/en/latest/api/ticket/articles.html), [Zammad community: MCP and AI agentic integration](https://community.zammad.org/t/mcp-and-ai-agentic-integration/19660)

## For AI agents

```text
Zammad has a full REST API but no official MCP server (checked 22 Oct 2026). The API docs say it allows all operations the UI has, and it needs an access token or OAuth set up on your own instance, which an admin can switch off. In a Zammad community thread in February 2026, replies said there is no MCP server, that the request would be considered, and that unaffiliated open-source servers exist.
Cotlet provides a hosted MCP server and REST API for Zammad: 14 tools (7 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=zammad, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    zammad_read, zammad_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/zammad, each operation at its own route, e.g. PATCH /api/v1/zammad/tickets/{ticket_id}
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   search_tickets, list_overviews, list_overview_tickets, get_ticket, list_ticket_articles, list_ticket_options, list_macros, update_ticket, add_tag, remove_tag, add_internal_note, reply_to_customer, run_macro, merge_tickets
Confirm      update_ticket, add_internal_note, reply_to_customer, run_macro, merge_tickets (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/zammad-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=zammad, requests Zammad in the Cotlet console and creates an API key there.
2. The user signs in to Zammad once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Zammad 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 Zammad 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 Zammad 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 Zammad 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 Zammad 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 Zammad 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 Zammad's terms; Cotlet is not affiliated with Zammad.
```

## What can an AI agent do in Zammad?

Cotlet is best for Zammad support teams who want an AI agent to triage tickets, chase pending ones and merge duplicates without running or fixing a server.

- **[Triage new support tickets](https://cotlet.dev/integrations/zammad-api-mcp-server/triage-new-tickets.md)** (runs: daily): "Go through Unassigned & Open Tickets in Zammad. Set the group and priority from what the customer wrote, assign billing questions to Nora Weiss, add a tag and leave a one-line internal note with the reason. Leave unclear ones for me." → `list_overview_tickets`, `get_ticket`, `list_ticket_articles`, `list_ticket_options`, `update_ticket`, `add_tag`, `add_internal_note`
- **[Follow up on pending tickets](https://cotlet.dev/integrations/zammad-api-mcp-server/follow-up-on-pending-tickets.md)** (runs: daily): "Open Pending Reached Tickets in Zammad. For each one where the customer still owes an answer, send a short follow-up on the thread, then set the ticket to pending close for 3 days. Leave tickets where the customer replied for me." → `list_overview_tickets`, `list_ticket_articles`, `reply_to_customer`, `update_ticket`
- **[Merge duplicate tickets](https://cotlet.dev/integrations/zammad-api-mcp-server/merge-duplicate-tickets.md)** (runs: weekly): "Find open Zammad tickets from the same customer about the same issue this week. Merge each newer duplicate into the original, and leave a note on the original. List pairs you are unsure about instead of merging them." → `search_tickets`, `get_ticket`, `list_ticket_articles`, `merge_tickets`, `add_internal_note`
- **Close and tag spam tickets** (runs: daily): "Look at new tickets in Zammad and run the Close & Tag as Spam macro on the ones that are clearly spam. List anything you are unsure about." → `list_overview_tickets`, `get_ticket`, `list_macros`, `run_macro`
- **Daily escalated tickets digest** (runs: daily): "Read the Escalated Tickets overview in Zammad and send me a short list: customer, group, owner and what the last message asked." → `list_overview_tickets`, `list_ticket_articles`

## Can Zammad automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Zammad 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 triage new support tickets, 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/zammad/overview-tickets. | 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/zammad/overview-tickets with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 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 Zammad.

### search_tickets

Zammad's own ticket search: free text or attributes such as state.name and customer.lastname. Access: read. REST: `GET /api/v1/zammad/tickets/search`. MCP: `zammad_read → search_tickets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | What you would type in Zammad's search bar, e.g. 'invoice' or 'state.name:open AND customer.lastname:Hill'. |
| `limit` | integer | no | How many tickets to return in one call. The rest follow with cursor. |
| `cursor` | string | no | Next page cursor from the previous call. |

Runs the query as if you typed it in the search bar, so Zammad's advanced search syntax works (for example state.name:open AND customer.lastname:Hill). Returns the tickets your account can see, with number, title, customer, state, priority, group and owner, and next_cursor when there are more. Zammad asks for English state names unless your instance has custom states. Reads nothing but the list; open a ticket with get_ticket.

Example response:

```json
{
  "tickets": [
    {
      "ticket_id": 4821,
      "number": "31004821",
      "title": "Invoice address change",
      "customer": "Dana Hill",
      "state": "open",
      "priority": "2 normal",
      "group": "Billing",
      "owner": "Nora Weiss",
      "created_at": "2026-10-21T08:12:00.000Z"
    }
  ],
  "next_cursor": null
}
```

### list_overviews

The ticket overviews your account sees, such as Unassigned & Open Tickets. Access: read. REST: `GET /api/v1/zammad/overviews`. MCP: `zammad_read → list_overviews`.

No parameters.

Returns the names of the overviews in the Overviews menu. Zammad ships My Assigned Tickets, Unassigned & Open Tickets, My Pending Reached Tickets, Open Tickets, Pending Reached Tickets and Escalated Tickets, and your admin may have added more. Use a name as the overview parameter of list_overview_tickets.

Example response:

```json
{
  "overviews": [
    {
      "name": "My Assigned Tickets"
    },
    {
      "name": "Unassigned & Open Tickets"
    },
    {
      "name": "Pending Reached Tickets"
    },
    {
      "name": "Escalated Tickets"
    }
  ]
}
```

### list_overview_tickets

Tickets in one overview with state, priority, group, owner and article count. Access: read. REST: `GET /api/v1/zammad/overview-tickets`. MCP: `zammad_read → list_overview_tickets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `overview` | string | yes | Overview name from list_overviews, e.g. 'Unassigned & Open Tickets'. |
| `limit` | integer | no | How many tickets to return in one call. The rest follow with cursor. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the tickets of one overview, as the overview page shows them, with number, title, customer, state, priority, group, owner, article_count and last update. Zammad decides which tickets belong to an overview by its conditions, and your account sees only the tickets of its groups. Pass next_cursor back as cursor for the next page. Pass ticket_id to get_ticket for the full ticket.

Example response:

```json
{
  "overview": "Unassigned & Open Tickets",
  "tickets": [
    {
      "ticket_id": 4812,
      "number": "31004812",
      "title": "Refund for a double charge",
      "customer": "Dana Hill",
      "state": "new",
      "priority": "2 normal",
      "group": "Users",
      "owner": null,
      "article_count": 4,
      "updated_at": "2026-10-22T07:40:00.000Z"
    },
    {
      "ticket_id": 4815,
      "number": "31004815",
      "title": "Cannot reset my password",
      "customer": "Leo Brandt",
      "state": "new",
      "priority": "2 normal",
      "group": "Users",
      "owner": null,
      "article_count": 9,
      "updated_at": "2026-10-22T07:52:00.000Z"
    }
  ],
  "next_cursor": null
}
```

### get_ticket

One ticket with its attributes, customer and tags, without the messages. Access: read. REST: `GET /api/v1/zammad/tickets/{ticket_id}`. MCP: `zammad_read → get_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from search_tickets, list_overview_tickets or the ticket address (#ticket/zoom/{ticket_id}). |

Returns the ticket sidebar of one ticket: title, number, state, priority, group, owner, customer with organization, tags, created and updated times, and pending_until when the state is a pending one. The messages come from list_ticket_articles. A ticket outside your account's groups returns APP_PERMISSION_DENIED.

Example response:

```json
{
  "ticket_id": 4790,
  "number": "31004790",
  "title": "Invoice address change",
  "state": "pending reminder",
  "priority": "2 normal",
  "group": "Billing",
  "owner": "Nora Weiss",
  "customer": {
    "name": "Dana Hill",
    "email": "dana.hill@example.com",
    "organization": "Northwind Studio"
  },
  "tags": [
    "invoice"
  ],
  "pending_until": "2026-10-21T09:00:00.000Z",
  "created_at": "2026-10-14T10:05:00.000Z",
  "updated_at": "2026-10-15T13:20:00.000Z"
}
```

### list_ticket_articles

The messages and notes of a ticket, oldest first, with sender, type and visibility. Access: read. REST: `GET /api/v1/zammad/ticket-articles`. MCP: `zammad_read → list_ticket_articles`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from search_tickets, list_overview_tickets or the ticket address (#ticket/zoom/{ticket_id}). |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns every article of the ticket in order. type is email, phone, web or note, sender is Agent, Customer or System, and internal is true for articles the customer cannot see. body is plain text; attachments are listed by file name and are not downloaded. A long thread comes in pages: pass next_cursor back as cursor.

Example response:

```json
{
  "articles": [
    {
      "article_id": 9034,
      "type": "email",
      "sender": "Customer",
      "internal": false,
      "from": "Dana Hill <dana.hill@example.com>",
      "subject": "Invoice address change",
      "body": "Hi, we moved offices. Please change the address on our invoices.",
      "attachments": [],
      "created_at": "2026-10-14T10:05:00.000Z"
    },
    {
      "article_id": 9047,
      "type": "email",
      "sender": "Agent",
      "internal": false,
      "from": "Nora Weiss",
      "subject": "Invoice address change",
      "body": "Hi Dana, which invoices should carry the new address, and what is it?",
      "attachments": [],
      "created_at": "2026-10-15T13:20:00.000Z"
    }
  ],
  "next_cursor": null
}
```

### list_ticket_options

The groups, owners, states and priorities your account can set on a ticket. Access: read. REST: `GET /api/v1/zammad/ticket-options`. MCP: `zammad_read → list_ticket_options`.

No parameters.

Returns the values the ticket sidebar offers your account: groups, agents who can be owner, states and priorities with their names exactly as Zammad shows them. Zammad ships the states new, open, pending reminder, pending close, closed and merged, and the priorities 1 low, 2 normal and 3 high; admins can add more. Call it before update_ticket so a name from your rule is checked first.

Example response:

```json
{
  "groups": [
    "Users",
    "Billing",
    "Support"
  ],
  "owners": [
    "Nora Weiss",
    "Sam Okafor"
  ],
  "states": [
    "new",
    "open",
    "pending reminder",
    "pending close",
    "closed"
  ],
  "priorities": [
    "1 low",
    "2 normal",
    "3 high"
  ]
}
```

### list_macros

Macros your account can run on a ticket, such as Close & Tag as Spam. Access: read. REST: `GET /api/v1/zammad/macros`. MCP: `zammad_read → list_macros`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | no | Only macros that apply to this ticket's group. |

Returns the names of the macros in the ticket's Update menu. Admins create macros under Manage > Macros and limit each to groups, so pass ticket_id to see the ones that fit that ticket. Zammad ships Close & Tag as Spam, which makes you the owner, adds the tag spam and closes the ticket.

Example response:

```json
{
  "macros": [
    {
      "name": "Close & Tag as Spam"
    },
    {
      "name": "Hand over to Billing"
    }
  ]
}
```

### update_ticket

Change a ticket's state, priority, group, owner or title. Access: write, asks the user first. REST: `PATCH /api/v1/zammad/tickets/{ticket_id}`. MCP: `zammad_write → update_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from search_tickets, list_overview_tickets or the ticket address (#ticket/zoom/{ticket_id}). |
| `state` | string | no | State name from list_ticket_options, e.g. open, pending reminder, pending close or closed. |
| `priority` | string | no | Priority name from list_ticket_options, e.g. '3 high'. |
| `group` | string | no | Group name from list_ticket_options. |
| `owner` | string | no | Agent name from list_ticket_options. |
| `pending_until` | datetime | no | ISO date and time. Required with state pending reminder or pending close. |
| `title` | string | no | New ticket title. It is also the subject of email articles. |

Sets only the fields you pass and returns the ticket as it is afterwards. Names must match list_ticket_options. A pending state needs pending_until, because Zammad asks for a date and time; Pending Close closes the ticket then. The first update of a new ticket moves it to open. Zammad's own triggers and notifications run as for any update by an agent, so a customer can get a mail from them. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": 4812,
  "number": "31004812",
  "title": "Refund for a double charge",
  "state": "open",
  "priority": "3 high",
  "group": "Billing",
  "owner": "Nora Weiss",
  "updated_at": "2026-10-22T08:03:00.000Z"
}
```

### add_tag

Add a tag to a ticket. Access: write. REST: `POST /api/v1/zammad/tickets/{ticket_id}/tags`. MCP: `zammad_write → add_tag`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from search_tickets, list_overview_tickets or the ticket address (#ticket/zoom/{ticket_id}). |
| `tag` | string | yes | Tag name, e.g. 'refund'. |

Adds one tag and returns the ticket's tags. A tag that does not exist is created only if your account may create tags, otherwise the call fails and says so. A tag reaches no customer and one remove_tag call undoes it, so it does not wait for your OK. Tags do not necessarily start a Zammad trigger.

Example response:

```json
{
  "ticket_id": 4812,
  "tags": [
    "refund",
    "billing"
  ]
}
```

### remove_tag

Remove a tag from a ticket. Access: write. REST: `DELETE /api/v1/zammad/tickets/{ticket_id}/tags`. MCP: `zammad_write → remove_tag`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from search_tickets, list_overview_tickets or the ticket address (#ticket/zoom/{ticket_id}). |
| `tag` | string | yes | Tag name to remove. |

Removes one tag from one ticket and returns the ticket's tags. The tag itself stays in Zammad for other tickets. It reaches no customer and add_tag undoes it, so it does not wait for your OK.

Example response:

```json
{
  "ticket_id": 4812,
  "tags": [
    "billing"
  ]
}
```

### add_internal_note

Write a note on a ticket that the customer cannot see. Access: write, asks the user first. REST: `POST /api/v1/zammad/tickets/{ticket_id}/internal-notes`. MCP: `zammad_write → add_internal_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from search_tickets, list_overview_tickets or the ticket address (#ticket/zoom/{ticket_id}). |
| `body` | string | yes | Note text. |

Adds a note article with internal visibility and returns it. Colleagues see it in the ticket, and a mention such as @Nora Weiss in the body notifies that agent. The customer sees nothing and no email goes out. Zammad lets only the author delete an article, and only within 10 minutes, and Cotlet has no delete, so each note waits for you. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "article_id": 9071,
  "ticket_id": 4812,
  "type": "note",
  "internal": true,
  "created_at": "2026-10-22T08:04:00.000Z"
}
```

### reply_to_customer

Send an email reply to the customer on the ticket's thread. Access: write, asks the user first. REST: `POST /api/v1/zammad/tickets/{ticket_id}/customer/replies`. MCP: `zammad_write → reply_to_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from search_tickets, list_overview_tickets or the ticket address (#ticket/zoom/{ticket_id}). |
| `body` | string | yes | Reply text. |
| `cc` | string | no | Comma-separated email addresses to copy. |

Adds an email article from you, visible to the customer, and Zammad sends it to the ticket's customer. The ticket title is the subject. Returns the new article with its recipient. Tickets from channels other than email return an error. A sent reply cannot be deleted through Cotlet. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "article_id": 9071,
  "ticket_id": 4790,
  "type": "email",
  "sender": "Agent",
  "internal": false,
  "to": "dana.hill@example.com",
  "subject": "Invoice address change",
  "created_at": "2026-10-22T08:05:00.000Z"
}
```

### run_macro

Apply a macro to a ticket, as the Update menu does. Access: write, asks the user first. REST: `POST /api/v1/zammad/tickets/{ticket_id}/macro/run`. MCP: `zammad_write → run_macro`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from search_tickets, list_overview_tickets or the ticket address (#ticket/zoom/{ticket_id}). |
| `macro` | string | yes | Macro name from list_macros. |

Applies the named macro to the ticket at once and returns the ticket afterwards. A macro can change state, priority, group and owner, add tags and notes, send a notification or run an AI agent, so what happens depends on how your admin built it. If the ticket lacks a required attribute that the macro does not set, Zammad applies none of its actions and the call returns that error. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": 4830,
  "macro": "Close & Tag as Spam",
  "state": "closed",
  "owner": "Nora Weiss",
  "tags": [
    "spam"
  ]
}
```

### merge_tickets

Merge a duplicate ticket into another ticket. Access: write, asks the user first. REST: `POST /api/v1/zammad/source-tickets/{source_ticket_id}/tickets/merge`. MCP: `zammad_write → merge_tickets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `source_ticket_id` | integer | yes | The duplicate. It ends up in state merged. |
| `target_ticket_id` | integer | yes | The original ticket that keeps all the articles. |

Moves all articles of the source ticket into the target ticket. The source stays, with its articles replaced by a merged label, the state merged and a link to the target. Returns both ticket ids and the new state of the source. Merging two tickets from different channels means you answer through the target's channel. A merge is not undone in one call, so check the pair. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "target_ticket_id": 4790,
  "target_number": "31004790",
  "source_ticket_id": 4821,
  "source_state": "merged"
}
```

## How do I connect Zammad to Claude Code, Codex or Cursor?

Connecting Zammad takes three steps: sign up, sign in to Zammad 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 Zammad to your agent.

1. **Create an account** Sign up and add Zammad in the console. Your API key is there too.

2. **Sign in to Zammad in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Zammad 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 Zammad 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.

```
Go through Unassigned & Open Tickets in Zammad. Set the group and priority from what the customer wrote, assign billing questions to Nora Weiss, add a tag and leave a one-line internal note with the reason. Leave unclear ones for me.
```

### Call Zammad 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/zammad 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/zammad/tickets/4812 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"group":"Billing","priority":"3 high","owner":"Nora Weiss"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "ticket_id": 4812,
  "number": "31004812",
  "title": "Refund for a double charge",
  "state": "open",
  "priority": "3 high",
  "group": "Billing",
  "owner": "Nora Weiss",
  "updated_at": "2026-10-22T08:03:00.000Z"
}
```

## Why use Cotlet for Zammad?

**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 Zammad 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 Zammad changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Zammad to Cotlet?

Yes. You sign in to Zammad yourself, in your own Cloud Browser, and we never save your password. Your agents only get Zammad 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 Zammad integration?**

No, Cotlet is independent of Zammad. Zammad's own API is too limited for this work. Cotlet works through your own Zammad account, the way you use Zammad 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 Zammad in your console: your agents lose access at once and you stay signed in. Signing out of Zammad in the browser works too, and Reset browser deletes the whole profile.

## Is there a Zammad MCP server on GitHub?

Yes. Community Zammad MCP servers exist on GitHub, usually maintained by one person; the Zammad community thread says so too and warns they are not affiliated with Zammad. You install one yourself, give it an API token from your instance, and fix it when Zammad changes. Cotlet hosts the same kind of server for you, signs in as your agent user, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, create an access token in your Zammad profile, store it, add the server to each MCP client | Sign up, sign in to Zammad once, add one MCP server or API key |
| When Zammad 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 Zammad access | A token in a file on your computer, readable by any program you run, with the rights of the user who made it | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until you make a new token or sign in again by hand | Your Cloud Browser keeps you signed in; if Zammad 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 Zammad 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 Zammad API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Zammad 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 20 to 30 credits (25 for most tools, about $0.10 to $0.15), 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 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $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 Zammad 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 Zammad 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 Zammad only after you enable it. When Zammad 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 Zammad, sign out of Zammad 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.
- **Zammad's terms:** You use your own Zammad account and stay responsible for following Zammad's terms. Cotlet is independent and not affiliated with Zammad. [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 Zammad in the console and press Request access. Then you create your API key and connect Zammad there.

**Do I need to be technical?**

No. You sign in to Zammad 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 Zammad to Cotlet?**

Yes. You sign in to Zammad yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Zammad 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 Zammad 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 Zammad 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 Zammad's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Zammad 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 Zammad 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?**

Zammad 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).

**Do I need an API token or admin rights in Zammad?**

No token. You sign in as an agent user, and what your agent can do follows that user's role and group permissions: Zammad shows an account only the tickets of its groups. Token access, which the REST API uses, can be switched off on an instance, and Cotlet does not depend on it. Running macros needs a macro your admin built for that group.

**Does it work with self-hosted Zammad?**

Yes, if the address of your instance opens from the internet, as it does for Zammad cloud. Your Cloud Browser opens it like any browser. An instance reachable only from an office network or a VPN cannot be reached from the Cloud Browser.

**Can my agent post or send messages in Zammad without asking me?**

No. Every call to update_ticket, add_internal_note, reply_to_customer, run_macro or merge_tickets waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_tag, remove_tag runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Zammad 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/zammad 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 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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.