← All launches
Zammad MCP by usefulapi logo
0 Report

Zammad MCP by usefulapi

by FastDrop

MCP Verified 1 hour ago Registry import free

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

Search and read Zammad tickets, customers and organizations; add notes, replies and ticket updates. Official MCP Registry: io.usefulapi/zammad@1.0.0. Remote endpoint: https://zammad.usefulapi.io/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.usefulapi/zammad and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 12 Oct 2026. Not supplied by the maker.

  • 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:2000

  • 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).

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

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.

Sign in to claim this listing

Matched on shared tags and the tools their MCP servers actually expose.

Reviews

Sign in to leave a review.

No reviews yet.

Comments

Sign in to join the discussion.

No comments yet - start the discussion.