Zammad MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Zammad MCP by usefulapi is answering right now. Last checked 10 min ago. It exposes 19 tools. Last commit 1 Nov 2026.

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

Uptime history 20 days of history

20 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

169 ms

Response time

average over 24h

Stars

last commit 1 Nov 2026

What changed 24

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 October 2026. No other catalogue keeps this.

31 Oct a tool changed version4 times that day

30 Oct a tool changed version2 times that day

29 Oct a tool changed version2 times that day

28 Oct a tool changed version2 times that day

27 Oct a tool changed version

25 Oct a tool changed version4 times that day

24 Oct a tool changed version3 times that day

23 Oct a tool changed version

22 Oct a tool changed version

20 Oct a tool changed version3 times that day

and 14 more, back to 13 October 2026

Nothing serious here today

Today is the operative word: we check Zammad MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://zammad.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.zammad]
url = "https://zammad.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "zammad": {
      "url": "https://zammad.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "zammad": {
      "type": "http",
      "url": "https://zammad.usefulapi.io/mcp"
    }
  }
}

Available tools 19

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

zammad

zammad_add_internal_note

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.

zammad_create_ticket

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.

zammad_get_me

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.

zammad_get_organization

One organization by id: name, domain, notes, VIP flag, member ids. GET /api/v1/organizations/{id}.

zammad_get_ticket

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.

zammad_get_ticket_article

One article by its id with its full body, headers and attachment names. GET /api/v1/ticket_articles/{id}.

zammad_get_user

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.

zammad_list_groups

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.

zammad_list_organizations

List customer organizations with domain, VIP flag and member ids. Needs an agent token. GET /api/v1/organizations.

zammad_list_ticket_articles

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}.

zammad_list_ticket_priorities

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.

zammad_list_ticket_states

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.

zammad_list_ticket_tags

The tags on one ticket. GET /api/v1/tags?object=Ticket&o_id={ticket_id}. Needs an agent token.

zammad_list_tickets

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.

zammad_reply_to_ticket

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.

zammad_search_organizations

Search customer organizations by name or domain. Needs an agent token. GET /api/v1/organizations/search.

zammad_search_tickets

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:"[email protected]"`, `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.

zammad_search_users

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.

zammad_update_ticket

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}.

Endpoints

URL	Transport	State	Latency	Checked
https://zammad.usefulapi.io/mcp	streamable-http	answering	141 ms	10 min ago

Alternatives to Zammad MCP by usefulapi

same job, measured the same way

Deskpro MCP by usefulapi

by usefulapi

Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies.

20 tools answering

RepairDesk MCP by usefulapi

by usefulapi

Read tickets, customers, stock and invoices; add confirmed internal ticket notes.

17 tools answering

ServiceMonster MCP by usefulapi

by usefulapi

Read ServiceMonster customers, jobs, orders and schedules, and add customer notes.

29 tools answering

MoeGo MCP by usefulapi

by usefulapi

Read customers, pets, appointments, orders and reports; add customer notes in MoeGo.

31 tools answering

Pobuca Connect MCP by usefulapi

by usefulapi

Read and update Pobuca Connect contacts and organizations; look up teams and custom fields.

17 tools answering

Orb MCP by usefulapi

by usefulapi

Read Orb customers, subscriptions, invoices, usage and costs; create or update customers.

26 tools answering

Veeqo MCP by usefulapi

by usefulapi

Read Veeqo orders, products, stock, warehouses, customers and POs; add notes, tag, set stock.

22 tools answering

Kayako MCP by usefulapi

by usefulapi

Search Kayako cases, replies, customers and help-center articles, and reply to or create cases.

21 tools answering

Zammad MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Zammad MCP by usefulapi do?

It exposes 19 tools, read directly from the server on our last check. Among them: zammad_add_internal_note, zammad_create_ticket, zammad_get_me, zammad_get_organization, zammad_get_ticket, zammad_get_ticket_article and 13 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Zammad MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 169 ms. The bar chart above shows every period we have measured.

How do I connect Zammad MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Zammad MCP by usefulapi need an API key?

No. Zammad MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 19 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Zammad MCP by usefulapi?

It answers our handshake in 169 ms on average, which is faster than 79% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Zammad MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at zammad.usefulapi.io, which runs on its operator's own terms.