Zammad logo zammad.com

Live

Zammad API and MCP server

Zammad's API needs an access token set up on your own instance, and Zammad offers no official tools for AI agents. Sign in to Zammad once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with Zammad.

Zammad has no API for this. So we run one for you.

Zammad's own API, a GitHub MCP server and Cotlet compared
What you need Zammad's APIGitHub MCP serverCotlet
Agent tools, macros, merges No Partly Yes, 14 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Zammad changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 22, 2026. Sources: Zammad API: Introduction (authentication, scope) · Zammad API: Tickets · Zammad API: Ticket articles · Zammad community: MCP and AI agentic integration

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Zammad in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Zammad to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 14 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Zammad and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    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"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/zammad with its own method and path, such as PATCH /api/v1/zammad/tickets/{ticket_id}, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Zammad API and MCP server do?

14 tools on your own Zammad account. Agents call them as operations of the MCP tools zammad_read and zammad_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
Zammad tools in Cotlet's MCP server and REST API
Tool What it does Access
search_tickets Zammad's own ticket search: free text or attributes such as state.name and customer.lastname. read
list_overviews The ticket overviews your account sees, such as Unassigned & Open Tickets. read
list_overview_tickets Tickets in one overview with state, priority, group, owner and article count. read
get_ticket One ticket with its attributes, customer and tags, without the messages. read
list_ticket_articles The messages and notes of a ticket, oldest first, with sender, type and visibility. read
list_ticket_options The groups, owners, states and priorities your account can set on a ticket. read
list_macros Macros your account can run on a ticket, such as Close & Tag as Spam. read
update_ticket Change a ticket's state, priority, group, owner or title. writeasks first
add_tag Add a tag to a ticket. write
remove_tag Remove a tag from a ticket. write
add_internal_note Write a note on a ticket that the customer cannot see. writeasks first
reply_to_customer Send an email reply to the customer on the ticket's thread. writeasks first
run_macro Apply a macro to a ticket, as the Update menu does. writeasks first
merge_tickets Merge a duplicate ticket into another ticket. writeasks first

Scroll the table for all 14 tools.

Ask in plain words. Your agent does the rest.

All Zammad use cases

Is it safe to connect Zammad?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the Zammad API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Zammad is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
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.

Questions

Does Zammad have an 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.

How do I get access?

Sign up free, open Zammad under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 14 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Zammad yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Zammad sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: update_ticket, add_internal_note, reply_to_customer, run_macro, merge_tickets wait for your OK by default. You can switch that off per tool for scheduled runs.

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.

Should I use a Zammad MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Zammad changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

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 Cotlet affiliated with Zammad?

No. Cotlet is independent and not affiliated with Zammad.

Give your agent access to Zammad.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free