Zammad MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.3.3 · published by io.usefulapi

Search and read Zammad tickets, customers and organizations; add notes, replies and ticket updates.

Deletes · 4

Compare Registry entry

19 tools: 4 can delete or cancel things and 15 only read.

Scanned Oct 21, 2026

Deletes or cancels4Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things0Claude Code: ask
Only reads15Claude Code: allow: see these tools

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http zammad https://zammad.usefulapi.io/mcp

Findings

Matches of fixed checks, with the text they matched.

2 info

Infozammad_search_users
The description mentions "credentials".
Matched text
description: "...rganization. Returns profile fields (no credentials). Needs an agent token. GET /api/v1/use..."
What this check looks for
Infozammad_get_user
The description mentions "credentials".
Matched text
description: "...nization, roles, VIP flag and notes. No credentials. GET /api/v1/users/{id}?expand=true."
What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

19 tools

Deletes or cancels 4Removes, cancels or revokes something.Claude Code: deny

zammad_add_internal_noteWRITE: add an INTERNAL note (visible to agents only, never e-mailed to the customer) to ONE ticket.No findings
Why it is in this group
- The name "zammad_add_internal_note" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: add an INTERNAL note (visible to agents only, never e-mailed to the customer) to ONE ticket. Needs an agent's token (a customer's token is refused, because Zammad would make the note public). The ticket's other data is not changed. POST /api/v1/ticket_articles with type=note, internal=true.
Annotations the server declares
- title: Add internal note
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
zammad_create_ticketWRITE: create ONE new ticket for an EXISTING customer (by e-mail address or user id) in a group, with a first article recorded as written by the customer (type note or phone).No findings
Why it is in this group
- The name "zammad_create_ticket" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: create ONE new ticket for an EXISTING customer (by e-mail address or user id) in a group, with a first article recorded as written by the customer (type note or phone). It does not send an e-mail by itself, but the instance's triggers may (for example an automatic confirmation to the customer). It never creates new users. POST /api/v1/tickets.
Annotations the server declares
- title: Create ticket
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
zammad_reply_to_ticketWRITE: send a customer-visible reply on ONE ticket.No findings
Why it is in this group
- The name "zammad_reply_to_ticket" says "reply": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: send a customer-visible reply on ONE ticket. THIS E-MAILS A REAL PERSON: the reply is delivered by e-mail to exactly ONE recipient and cannot be recalled. By default the recipient is the ticket's customer (looked up from the ticket); `to` may name one other single address. No cc, no bulk, no attachments. Needs an agent's token (a customer's token is refused). For an internal remark use zammad_add_internal_note. GET /api/v1/tickets/{id}, then POST /api/v1/ticket_articles with type=email, internal=false.
Annotations the server declares
- title: Reply to ticket (e-mails the customer)
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
zammad_update_ticketWRITE: change fields of ONE ticket: state, priority, owner (agent), group and/or title.No findings
Why it is in this group
- The name "zammad_update_ticket" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: change fields of ONE ticket: state, priority, owner (agent), group and/or title. Use names from zammad_list_ticket_states / zammad_list_ticket_priorities / zammad_list_groups. Pending states need `pending_time`. Never deletes, removes or merges (those states are refused). The instance's own triggers still run, so closing or reassigning a ticket can send the customer or agent a notification e-mail. PUT /api/v1/tickets/{id}.
Annotations the server declares
- title: Update ticket
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true

Only reads 15Looks things up and changes nothing.Claude Code: allow

zammad_get_meThe Zammad user this access token belongs to: id, name, e-mail, roles and groups.No findings
Why it is in this group
- The name "zammad_get_me" says "get": a word for reading.
Description, as the server wrote it
The Zammad user this access token belongs to: id, name, e-mail, roles and groups. Use it to confirm the connection and the token's permissions. GET /api/v1/users/me.
Annotations the server declares
- title: Get current user
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_get_organizationOne organization by id: name, domain, notes, VIP flag, member ids.No findings
Why it is in this group
- The name "zammad_get_organization" says "get": a word for reading.
Description, as the server wrote it
One organization by id: name, domain, notes, VIP flag, member ids. GET /api/v1/organizations/{id}.
Annotations the server declares
- title: Get organization
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_get_ticketOne ticket by its numeric id (not the ticket number): title, group, state, priority, owner, customer, organization, dates, escalation and article count.No findings
Why it is in this group
- The name "zammad_get_ticket" says "get": a word for reading.
Description, as the server wrote it
One ticket by its numeric id (not the ticket number): title, group, state, priority, owner, customer, organization, dates, escalation and article count. GET /api/v1/tickets/{id}?expand=true.
Annotations the server declares
- title: Get ticket
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_get_ticket_articleOne article by its id with its full body, headers and attachment names.No findings
Why it is in this group
- The name "zammad_get_ticket_article" says "get": a word for reading.
Description, as the server wrote it
One article by its id with its full body, headers and attachment names. GET /api/v1/ticket_articles/{id}.
Annotations the server declares
- title: Get ticket article
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_get_userOne user (customer or agent) by id: name, e-mail, phone, organization, roles, VIP flag and notes.1 finding
Why it is in this group
- The name "zammad_get_user" says "get": a word for reading.
Findings
- Info
  The description mentions "credentials".
  Matched text
  description: "...nization, roles, VIP flag and notes. No credentials. GET /api/v1/users/{id}?expand=true."
  What this check looks for
Description, as the server wrote it
One user (customer or agent) by id: name, e-mail, phone, organization, roles, VIP flag and notes. No credentials. GET /api/v1/users/{id}?expand=true.
Annotations the server declares
- title: Get user
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_list_groupsThe ticket groups (queues) of the instance, with ids, names and agent ids.No findings
Why it is in this group
- The name "zammad_list_groups" says "list": a word for reading.
Description, as the server wrote it
The ticket groups (queues) of the instance, with ids, names and agent ids. Zammad requires the admin.group permission for this list; with an agent-only token it returns an authorization error. GET /api/v1/groups.
Annotations the server declares
- title: List groups
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_list_organizationsList customer organizations with domain, VIP flag and member ids.No findings
Why it is in this group
- The name "zammad_list_organizations" says "list": a word for reading.
Description, as the server wrote it
List customer organizations with domain, VIP flag and member ids. Needs an agent token. GET /api/v1/organizations.
Annotations the server declares
- title: List organizations
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_list_ticket_articlesAll articles (messages, internal notes, e-mails, phone notes) of one ticket in order, with sender, type, internal flag, from/to/cc, subject, body and attachment names (attachments …No findings
Why it is in this group
- The name "zammad_list_ticket_articles" says "list": a word for reading.
Description, as the server wrote it
All articles (messages, internal notes, e-mails, phone notes) of one ticket in order, with sender, type, internal flag, from/to/cc, subject, body and attachment names (attachments are not downloaded). Long bodies are cut at 6000 characters; use zammad_get_ticket_article for the full text. GET /api/v1/ticket_articles/by_ticket/{ticket_id}.
Annotations the server declares
- title: List ticket articles
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_list_ticket_prioritiesThe ticket priorities of the instance (e.g.No findings
Why it is in this group
- The name "zammad_list_ticket_priorities" says "list": a word for reading.
Description, as the server wrote it
The ticket priorities of the instance (e.g. '1 low', '2 normal', '3 high') with ids. Use the names in zammad_update_ticket. GET /api/v1/ticket_priorities.
Annotations the server declares
- title: List ticket priorities
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_list_ticket_statesThe ticket states of the instance (new, open, pending reminder, pending close, closed, ...) with ids and whether they are active.No findings
Why it is in this group
- The name "zammad_list_ticket_states" says "list": a word for reading.
Description, as the server wrote it
The ticket states of the instance (new, open, pending reminder, pending close, closed, ...) with ids and whether they are active. Use the names in zammad_update_ticket. GET /api/v1/ticket_states.
Annotations the server declares
- title: List ticket states
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_list_ticket_tagsThe tags on one ticket.No findings
Why it is in this group
- The name "zammad_list_ticket_tags" says "list": a word for reading.
Description, as the server wrote it
The tags on one ticket. GET /api/v1/tags?object=Ticket&o_id={ticket_id}. Needs an agent token.
Annotations the server declares
- title: List ticket tags
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_list_ticketsList the tickets the token's user can see (an agent sees the tickets of their groups; a customer only their own).No findings
Why it is in this group
- The name "zammad_list_tickets" says "list": a word for reading.
Description, as the server wrote it
List the tickets the token's user can see (an agent sees the tickets of their groups; a customer only their own). For anything targeted use zammad_search_tickets. GET /api/v1/tickets?expand=true.
Annotations the server declares
- title: List tickets
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_search_organizationsSearch customer organizations by name or domain.No findings
Why it is in this group
- The name "zammad_search_organizations" says "search": a word for reading.
Description, as the server wrote it
Search customer organizations by name or domain. Needs an agent token. GET /api/v1/organizations/search.
Annotations the server declares
- title: Search organizations
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_search_ticketsSearch tickets with Zammad's query syntax.No findings
Why it is in this group
- The name "zammad_search_tickets" says "search": a word for reading.
Description, as the server wrote it
Search tickets with Zammad's query syntax. With Elasticsearch on the instance you can use fields, e.g. `state.name:open AND group.name:Sales`, `customer.email:"a@b.com"`, `title:invoice`, `number:20001`; a plain word searches ticket text. Replies carry ids plus names (group, state, priority, owner, customer). GET /api/v1/tickets/search?expand=true.
Annotations the server declares
- title: Search tickets
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
zammad_search_usersSearch customers and agents by name, e-mail, login, phone or organization.1 finding
Why it is in this group
- The name "zammad_search_users" says "search": a word for reading.
Findings
- Info
  The description mentions "credentials".
  Matched text
  description: "...rganization. Returns profile fields (no credentials). Needs an agent token. GET /api/v1/use..."
  What this check looks for
Description, as the server wrote it
Search customers and agents by name, e-mail, login, phone or organization. Returns profile fields (no credentials). Needs an agent token. GET /api/v1/users/search?expand=true.
Annotations the server declares
- title: Search users
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.3.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http zammad https://zammad.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__zammad__zammad_get_me",
      "mcp__zammad__zammad_search_tickets",
      "mcp__zammad__zammad_list_tickets",
      "mcp__zammad__zammad_get_ticket",
      "mcp__zammad__zammad_list_ticket_articles",
      "mcp__zammad__zammad_get_ticket_article",
      "mcp__zammad__zammad_list_ticket_tags",
      "mcp__zammad__zammad_list_ticket_states",
      "mcp__zammad__zammad_list_ticket_priorities",
      "mcp__zammad__zammad_list_groups",
      "mcp__zammad__zammad_search_users",
      "mcp__zammad__zammad_get_user",
      "mcp__zammad__zammad_search_organizations",
      "mcp__zammad__zammad_list_organizations",
      "mcp__zammad__zammad_get_organization"
    ],
    "ask": [],
    "deny": [
      "mcp__zammad__zammad_add_internal_note",
      "mcp__zammad__zammad_reply_to_ticket",
      "mcp__zammad__zammad_update_ticket",
      "mcp__zammad__zammad_create_ticket"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as zammad. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/zammad/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 19:23 UTC.

For agents: Markdown · JSON · report this listing