io.usefulapi/zammad

up checked 2026-11-11T12:38:39.553Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

Zammad MCP by usefulapi

Publisher-provided description

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

Summary by lookupd

Search and read helpdesk tickets, customers and organizations; add internal notes, send replies and update ticket state, priority or owner.

Install

Claude Code, remote (streamable-http)

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

Codex, remote (streamable-http)

codex mcp add zammad --url https://zammad.usefulapi.io/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

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

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (19 tools)

Publisher-provided text

• 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/user
• 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:"
• 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_ticket
• 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 /ap
• 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
• 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
• 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
• 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/sear
• 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, becau
• 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
• 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_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

Details

• Version: 1.24.3
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 490 ms
• First indexed: 2026-11-01T10:06:57.835Z
• Last seen in registry: 2026-11-11T00:17:37.417Z
• Repository: https://github.com/m190/usefulapi-mcp
• Website: https://usefulapi.io/zammad/

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/io.usefulapi/zammad.svg)](https://lookupd.com/servers/io.usefulapi/zammad)

• 62071 servers
• Last crawl: 2026-11-11T16:39:06.253Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp