Zammad MCP server

Search and read Zammad tickets, customers and organizations; add notes, replies and ticket updates. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.

Connect Zammad50 free tool calls a month

What can I ask?

Turn on the Zammad connector, then ask in plain words. The AI picks the tools.

What you can do with Zammad in Claude and ChatGPT

For support agents and helpdesk managers who handle tickets in Zammad.

Find tickets by customer, state or keyword

The AI searches tickets with Zammad's query syntax, for example open tickets in a group or tickets from one customer email, and lists them with owner, state and priority.

Read a ticket conversation and summarize it

The AI opens a ticket and reads its articles, with messages, internal notes, e-mails and phone notes, and summarizes what happened.

Look up a customer or an organization

The AI searches users and organizations by name, e-mail, phone or domain, and opens one to show roles, VIP flag, notes and members.

Add an internal note to a ticket

The AI adds an internal note that only agents see to one ticket. The note is never e-mailed to the customer.

Changes data

Update a ticket's state, priority, owner, group or title

The AI changes the state, priority, owner, group or title of one ticket, using the names your Zammad uses. Triggers on your instance may send notification e-mails.

Changes data

Reply to a customer or open a new ticket

The AI sends a reply by e-mail to one recipient on a ticket, or creates a new ticket for an existing customer with a first article.

Changes data

How do I connect Zammad?

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.

Claude claude.ai · Desktop

  1. Open Customize → Connectors, then click + Add → Add custom connector.
  2. Enter the name Zammad and this URL, then click Add:
    https://zammad.usefulapi.io/mcp
  3. Claude opens the login page: enter your Zammad address and Zammad access token.
  4. In a chat, click + → Connectors and turn on Zammad.

Team and Enterprise: an Owner adds the connector for the organization first.

ChatGPT chatgpt.com

  1. Open Plugins, click +, then Add custom MCP server.
  2. Enter the name Zammad and this URL, choose OAuth as the authentication, confirm the warning and create it:
    https://zammad.usefulapi.io/mcp
  3. ChatGPT opens the login page: enter your Zammad address and Zammad access token.
  4. In Plugins, install Zammad, then choose it in a chat.

No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.

Claude Code

Run this command, then run /mcp in Claude Code to log in:

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

Cursor

Add to Cursor or add this to ~/.cursor/mcp.json:

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

VS Code

Add to VS Code or add this to .vscode/mcp.json:

{
  "servers": {
    "zammad": {
      "type": "http",
      "url": "https://zammad.usefulapi.io/mcp"
    }
  }
}

Codex

Run these commands. The second one opens the login page:

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

Other clients

Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.

https://zammad.usefulapi.io/mcp

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.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Proper user$9/mo · $90/yr10,000 tool calls / month
Pro+per user$39/mo · $390/yr100,000 tool calls / month

Each paid plan covers this Zammad server only. Ask your AI to run zammad_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with zammad_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with zammad_upgrade before then undoes the cancel. Or write to support@usefulapi.io.

Tools 23

Show all 23 tools (the AI picks them for you)

Read only · 15

  • Get current userzammad_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.
  • Search ticketszammad_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, state, priority, owner, customer).
  • List ticketszammad_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 ticketzammad_get_ticket
    One ticket by its numeric id (not the ticket number): title, group, state, priority, owner, customer, organization, dates, escalation and article count.
  • List ticket articleszammad_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 ticket articlezammad_get_ticket_article
    One article by its id with its full body, headers and attachment names.
  • List ticket tagszammad_list_ticket_tags
    The tags on one ticket. GET /api/v1/tags?object=Ticket&o_id={ticket_id}. Needs an agent token.
  • List ticket stateszammad_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.
  • List ticket prioritieszammad_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.
  • List groupszammad_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.
  • Search userszammad_search_users
    Search customers and agents by name, e-mail, login, phone or organization. Returns profile fields (no credentials). Needs an agent token.
  • Get userzammad_get_user
    One user (customer or agent) by id: name, e-mail, phone, organization, roles, VIP flag and notes. No credentials.
  • Search organizationszammad_search_organizations
    Search customer organizations by name or domain. Needs an agent token.
  • List organizationszammad_list_organizations
    List customer organizations with domain, VIP flag and member ids. Needs an agent token.
  • Get organizationzammad_get_organization
    One organization by id: name, domain, notes, VIP flag, member ids.

Changes data · 4

  • Add internal notezammad_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.
  • Reply to ticket (e-mails the customer)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 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.
  • Update ticketzammad_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.
  • Create ticketzammad_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.

Your usefulapi plan · 4

  • Usage status (free-tier meter)zammad_usage_status
    Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter.
  • Request a missing featurezammad_request_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.
  • Upgrade to Pro or Pro+zammad_upgrade
    Get a paid plan for Zammad (the free tier caps monthly usage). Pro: 10,000 tool calls a month, for normal use — plan "monthly" ($9/month) or "yearly" ($90/year, 2 months free). Pro+: 100,000 tool calls a month, for automations and heavy use — plan "plus" ($39/month) or "plus_yearly" ($390/year). Without a plan it returns both Pro and Pro+, each with a payment link, for the user to choose; with a plan, one link. An existing Pro subscription changes to Pro+ in place: call without confirm first, as the reply states the exact charge for this account (the price difference for the rest of the period, or in a free Pro trial the full Pro+ price, as the trial ends); then call with confirm: true. Cancel any time: the plan then runs to the end of the paid period, so it also suits a one-time job. A link opens Stripe Checkout in the browser; after payment the account upgrades automatically. Does not count against the meter.
  • Cancel the Pro subscriptionzammad_cancel_subscription
    Cancel the caller's Zammad Pro subscription at the end of the paid period (no refund for the current period; Pro continues 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.

FAQ

What can I do with Zammad in Claude or ChatGPT?

Find tickets by customer, state or keyword. Read a ticket conversation and summarize it. Look up a customer or an organization. Add an internal note to a ticket. Update a ticket's state, priority, owner, group or title. Reply to a customer or open a new ticket. See what you can do for the details.

Is this an official Zammad product?

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.

Can I connect Zammad to Claude or ChatGPT?

Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.

What do I need to connect?

The login page asks for your Zammad address and Zammad access token. See Before you connect for where to find them.

Do I put my Zammad key or an Authorization header in the client config?

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.

How do you keep my Zammad credentials?

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.

Can the AI change my Zammad data?

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.

What does it cost?

The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Zammad server only. Cancel any time: your paid plan then runs to the end of the paid period. Run zammad_usage_status to see how many calls you used.

How do I subscribe or cancel?

Ask the AI to run zammad_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run zammad_cancel_subscription. Your paid plan continues to the end of the paid period.

What if a Zammad tool that I need is missing?

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.

Which AI clients can I use?

Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, 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.

Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.

More Customer Support MCP servers

AteraChatwootDesk365DeskproeDeskEnchantFreshdeskGladlyGoreloHappyFoxHelpCrunchHelpwiseKayakoOctadeskRe:amazeSupportBeeTrengoUseResponseUserVoiceVision HelpdeskZendesk

All Customer Support servers →