# Zammad Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Zammad

Search, read and manage support tickets, customers and organizations in Zammad.

- Record: https://musedirectory.ai/connector/zammad
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/zammad/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 193ms, checked 2026-10-29T11:00:49Z
- Endpoint: https://zammad.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T08:06:10Z)
- Source: Found in the official MCP Registry (io.usefulapi/zammad) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fzammad

Connect to your Zammad help desk to search and read tickets, customers and organizations. Add internal notes, send customer replies, update ticket state and priority, and create new tickets for existing customers.

Example request: "Find all open tickets in the Sales group and add an internal note to the highest priority one."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Zammad to help me. It is a free service with an MCP server at https://zammad.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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:"a@b.com"`, `title:invoice`, `number:20001`; a plain word searches ticket text. Replies carry ids plus names (group, stat
- 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 f
- 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=no
- 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.
- 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). 
- 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 confirma

Screening checks:
- MCP handshake: pass (Answered in 184ms)
- Domain against threat feeds (Cloudflare security DNS): pass (zammad.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (19 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)