Search and read Zammad tickets, customers and organizations; add notes, replies and ticket updates. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"zammad": {
"url": "https://zammad.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"zammad": {
"type": "http",
"url": "https://zammad.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Zammad address and Zammad access token.
Zammad address: for Zammad Cloud just the name (acme for acme.zammad.com); for a self-hosted Zammad its public https:// address (https://support.example.com). Access token: in Zammad open your Profile → Token Access → Create and tick the permissions you want (ticket.agent for agents; admin.group only if you want the group list). The token acts with your user's permissions, so a dedicated agent user makes its activity easy to track. It is used only to call your Zammad on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Zammad address and Zammad access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
zammad_get_me | read | Get current user 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 | read | 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_list_tickets | read | 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 | read | 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 | read | 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_get_ticket_article | read | 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 | read | 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 | read | 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 | read | 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 | read | 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 | read | 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 | read | 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 | read | Search organizations Search customer organizations by name or domain. Needs an agent token. GET /api/v1/organizations/search. |
zammad_list_organizations | read | List organizations List customer organizations with domain, VIP flag and member ids. Needs an agent token. GET /api/v1/organizations. |
zammad_get_organization | read | Get organization One organization by id: name, domain, notes, VIP flag, member ids. GET /api/v1/organizations/{id}. |
zammad_add_internal_note | write | 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 | Reply to ticket (e-mails the customer) 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_update_ticket | write | 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}. |
zammad_create_ticket | write | 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_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
zammad_request_feature | Request a missing feature Tell usefulapi that the user needs something the Zammad tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
zammad_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Zammad tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
zammad_cancel_subscription | Cancel the Pro subscription Cancel the caller's Zammad Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run zammad_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this Zammad server only. Subscribe with zammad_upgrade (it returns a Stripe Checkout link). Cancel any time with zammad_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running zammad_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Zammad. The server calls the Zammad API with your own Zammad access, so it sees only the data that your account can see.
The login page asks for your Zammad address and Zammad access token. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Zammad address and Zammad access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Zammad API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Zammad.
Yes, if you approve it. 4 of the 19 Zammad tools can create or change data. The other 15 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Zammad server only. Run zammad_usage_status to see how many calls you used.
Ask the AI to run zammad_upgrade: it returns a Stripe Checkout link. To cancel, run zammad_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with zammad_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.