Zammad MCP server

What the model can do

Zammad help desk: search tickets by state, group, customer or words, read a ticket with its articles (replies and internal notes), ticket counts by state, users, organisations, groups, states and priorities. When you ask it can add an internal note or an email reply, create, update, close or delete a ticket, tag and link tickets, and create or update users and organisations.

Reads

• zammad_search_ticketsSearch Zammad tickets: by state (open, new, pending reminder, closed…), group, customer email, owner email, words in the title or articles…
• zammad_ticketOne Zammad ticket by id with its articles oldest first: each article's type (email, note, phone, web), sender (Agent, Customer, System)…
• zammad_ticket_countsHow many Zammad tickets are in each state (open, new, pending reminder, pending close, closed, merged…)…
• zammad_usersSearch Zammad users (customers and agents) by name, email or login: id, name, email, phone, department, organisation, roles, whether active or VIP…
• zammad_organizationsZammad organisations (customers' companies): name, domain, whether shared, VIP, member count, note and a link.
• zammad_referenceZammad's ticket states (with which are the defaults), priorities and groups, with their ids — the names the search and count tools take…

Acts, when you ask

These change something in Zammad. 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.

• zammad_add_articleAdds an article to a Zammad ticket — an internal note (default), a note the customer can see in the portal, or an email reply sent to the customer.
• zammad_create_ticketCreates a Zammad ticket in a group for a customer, with a first article that is an internal note by default…
• zammad_update_ticketChanges a Zammad ticket's title, group, state or priority, optionally adding an internal note saying why.
• zammad_close_ticketCloses a Zammad ticket (state "closed"), optionally with an internal note.
• zammad_tag_ticketAdds or removes a tag on a Zammad ticket.
• zammad_link_ticketsLinks two Zammad tickets with a normal link, so each shows the other; nobody is notified.
• zammad_create_userCreates a Zammad user with Zammad's default sign-up role (a customer); roles and passwords are not set from here.
• zammad_update_userUpdates a Zammad user's name, phone, department, organisation or note (only the fields given change).
• zammad_create_organizationCreates a Zammad organisation, optionally with a domain (and domain assignment…
• zammad_update_organizationUpdates a Zammad organisation's name, domain, note, VIP flag or whether it is active (only the fields given change; membership is not touched).
• zammad_delete_ticketPermanently deletes a Zammad ticket with all its articles and attachments; Zammad says this cannot be undone.

Connect it

First connect Zammad on Dashboard → Connections, then add Memtro to your client once. The Zammad tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

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

• › How many tickets are open in the Sales group and how many are pending reminder?
• › Which tickets from Lindqvist AB are still open and who owns them?
• › Show me ticket 1184 with the internal notes
• › Add an internal note to ticket 1184: replacement unit dispatched on 5 November, tracking sent
• › Reply to ticket 1190 that the parcel left today, then set it to pending close

Questions

Is this an official Zammad MCP server?

No. It is Memtro's MCP server with Memtro's Zammad connector behind it: the connector reads Zammad through its API with the credentials you connect on Dashboard → Connections, and Zammad 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 Zammad?

Only when you ask, and only what it has been granted: add an internal note or an email reply to a ticket; create a ticket; change a ticket's title, group, state or priority; close a ticket; tag or untag a ticket; link two tickets; create a user (customer); update a user's contact details; create an organisation; update an organisation; delete a ticket (permanent). 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.

Other MCP servers · Support

• Help Scout MCP server
• Zendesk MCP server
• Intercom MCP server
• Freshdesk MCP server
• Front MCP server
• Zoho Desk MCP server