Connect-MCP

Zammad MCP by usefulapi

io.usefulapi/zammad · v1.0.0

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

MCPremoteno credentialsCRM & salesEmailNews

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 19 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 19 tools · 15 read, 4 write (incl. delete/pay) · CRM & sales, Email, Knowledge & docs

Test call zammad_get_me: needs a key: HTTP 401 (984 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://zammad.usefulapi.io/mcp

Tools

19 tools listed at last check
  • 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_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,
  • 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_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_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/v
  • zammad_get_ticket_article One article by its id with its full body, headers and attachment names. GET /api/v1/ticket_articles/{id}.
  • 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_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_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_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_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_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_search_organizations Search customer organizations by name or domain. Needs an agent token. GET /api/v1/organizations/search.
  • zammad_list_organizations List customer organizations with domain, VIP flag and member ids. Needs an agent token. GET /api/v1/organizations.
  • zammad_get_organization One organization by id: name, domain, notes, VIP flag, member ids. GET /api/v1/organizations/{id}.
  • 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_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
  • 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 t
  • 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

Badge

Connect-MCP badge for io.usefulapi/zammad

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.usefulapi/zammad.svg)](https://clawy.uk/mcp/s/io.usefulapi/zammad)

Repository · Website