Skip to content

Helpdesk

Zammad MCP connector

The Zammad connector lets Claude, ChatGPT, Cursor, and any MCP client look up and update Zammad customers, organizations, groups, roles, and SLAs on your behalf, with each request running under your own Zammad access and recorded in an audit log.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Zammad to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Zammad once

  1. Open Connections, choose Add connection, and pick Zammad.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Zammad API key. One person generates a token in Zammad and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

zammad
Zammad
Acquire
Ada
Atomicwork
CM Mobile Service Cloud
Crisp
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Zammad to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Zammad to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Zammad to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Zammad to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Zammad through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Support

    Find a customer before you reply

    Ask for a customer by name or email and get their Zammad profile, the organization they belong to, and the SLA that applies, all before you write the first line of a reply.

  • Support

    Fix a customer record after a call

    When a caller gives you a new phone number, job title, or preferred name, say so in plain words and the Zammad user record is updated while you are still on the line.

  • Account management

    Set up a new client organization

    Create the organization in Zammad, add its domain and notes, and confirm which customers are attached to it, without opening the admin area.

  • Support operations

    Reorganize groups as the desk grows

    List every Zammad group, create a new one for a product line or region, and rename or retire groups that no longer match how the team works.

  • IT

    Review who holds which role

    Pull the list of Zammad roles and the agents assigned to each, spot anyone with more access than their job needs, and adjust the role in a sentence.

  • Customer success

    Check the SLA for an account

    Ask which SLA covers a given organization in Zammad and what response and update times it promises, so you can set expectations with the customer accurately.

Try asking

  • “Show open tickets in the Support group this week.”
  • “Which organizations filed the most tickets last month?”
  • “List Zammad users added to the Billing group.”

See all 98 Zammad tools below

AI tools

Zammad tools for your AI agents

98 tools are ready to call through Elaichi's MCP endpoint the moment you connect Zammad, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Zammad gets you

6 screens from the product, each doing one job for your Zammad account.

The agent

Ask about tickets, get real answers.

Type a question in plain language and read it from live Zammad records.

  • tickets
  • users
  • organizations
  • groups

Ask Elaichi to work across your apps.

Show open tickets in the Support group this week.

Which organizations filed the most tickets last month?

List Zammad users added to the Billing group.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Zammad.

One governed MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

98 Zammad tools ready to call.

Tickets, users, organizations and groups covered, with no custom code to write.

  • Zammad users get me
  • List all Zammad users
  • Update a Zammad user by ID
  • Delete a Zammad user by ID
ElaichiTools
Tool Action Description
Zammad users get me Get Get the currently authenticated Zammad user. Returns: active, address, authorization_ids, city, country, created_at, created_by_id, department, email, fax, firstname, group_ids, id, image, image_source, last_login, lastname, login, login_failed, mobile, note, organization_id, organization_ids, out_of_office, out_of_office_end_at, out_of_office_replacement_id, out_of_office_start_at, overview_sorting_ids, phone, preferences, role_ids, source, street, two_factor_preference_ids, updated_at, updated_by_id, verified, vip, web, zip.
List all Zammad users List List Zammad users. Returns per user: id, login, email, firstname, lastname, active, organization_id, role_ids, preferences, created_at, updated_at. Returns: active, address, authorization_ids, city, country, created_at, created_by_id, department, email, fax, firstname, group_ids, id, image, image_source, last_login, lastname, login, login_failed, mobile, note, organization_id, organization_ids, out_of_office, out_of_office_end_at, out_of_office_replacement_id, out_of_office_start_at, overview_sorting_ids, phone, preferences, role_ids, source, street, two_factor_preference_ids, updated_at, updated_by_id, verified, vip, web, zip.
Update a Zammad user by ID Update Update a Zammad user by id with attributes such as phone, department, and address. Returns the updated user object including id, login, email, firstname, lastname, active, role_ids, created_at, updated_at. Returns: active, address, authorization_ids, city, country, created_at, created_by_id, department, email, fax, firstname, group_ids, id, image, image_source, last_login, lastname, login, login_failed, mobile, note, organization_id, organization_ids, out_of_office, out_of_office_end_at, out_of_office_replacement_id, out_of_office_start_at, overview_sorting_ids, phone, preferences, role_ids, source, street, two_factor_preference_ids, updated_at, updated_by_id, verified, vip, web, zip. Required: id.
Delete a Zammad user by ID Delete Delete a Zammad user by id. This is a permanent removal that cannot be undone and may also remove related references such as tickets. Returns an empty 200 response with {} on success. Returns: empty response. Required: id.
Zammad users search Search Search Zammad users by query string. Returns matching user records including id, login, firstname, lastname, email, organization_id, active, vip, created_at, updated_at, role_ids, and group_ids. Returns: active, address, authorization_ids, city, country, created_at, created_by_id, department, email, fax, firstname, group_ids, id, image, image_source, last_login, lastname, login, login_failed, mobile, note, organization_id, organization_ids, out_of_office, out_of_office_end_at, out_of_office_replacement_id, out_of_office_start_at, overview_sorting_ids, phone, preferences, role_ids, source, street, two_factor_preference_ids, updated_at, updated_by_id, verified, vip, web, zip. Required: query.

Toolboxes

Every team gets its own toolbox.

Curate Zammad tools per team so support, ops and billing see different sets.

  • Support
  • Customer success
  • IT operations
  • Billing
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Zammad · tickets and replies

Zammad starter 18 Mar 4, 2026

Customer success toolbox

Zammad · organizations and accounts

9 Mar 2, 2026

IT operations toolbox

Zammad · users and groups

24 Feb 27, 2026

Billing toolbox

Zammad · invoice tickets

Zammad starter 6 Feb 19, 2026

Engineering toolbox

Zammad · escalated bug tickets

31 Jan 30, 2026

Quality toolbox

Zammad · ticket history and tags

12 Jan 22, 2026

Shared connections

Share a Zammad login, never the password.

Teammates work through a connection while the credential stays with whoever connected it.

  • Support EMEA
  • Support APAC
  • Tier 2 escalations
  • Customer success
ElaichiConnections
Connection Scope Status Access
ZA

Zammad (Support EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
ZA

Zammad (Support APAC)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
ZA

Zammad (Tier 2 escalations)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
ZA

Zammad (Customer success)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
ZA

Zammad (IT helpdesk)

Connected by Clara Nowak

Personal • Active Not shared
ZA

Zammad (Billing queue)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Zammad call is written down.

When, who, what happened, type and resource, in an append only log.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Zammad Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Zammad Tickets Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Zammad Tickets List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule drafts your ticket digest.

Zammad tickets are fetched, grouped, drafted by an agent, approved, then posted back.

Zammad digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch tickets

    Zammad

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Zammad

    Queued

Collections and dashboards

Helpdesk numbers arrive before anyone asks.

Four metrics, 14 days of tickets created and a team breakdown, refreshed on schedule.

Zammad health

Refreshed 4 minutes ago · every 15 minutes · from the tickets collection

Live

Tickets

1,284 ↓ 12%

Users

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Tickets created

Last 14 days

By team

Share of activity

Support EMEA 34%

Support APAC 27%

Tier 2 escalations 21%

Customer success 18%

FAQ

Frequently asked questions

How do I connect Zammad to Claude?

First, open Elaichi, choose Zammad, and paste in an API key from your Zammad profile, which takes about a minute. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and Zammad is available in your conversation.

Does Zammad work with ChatGPT and Cursor as well as Claude?

Yes. Once Zammad is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Zammad once and every client you use picks it up.

What can an AI agent actually do with my Zammad data?

With Zammad connected, an agent can find a customer by name or email, show which organization they belong to, update their contact details, create or edit organizations, manage groups and roles, and look up which SLA applies to an account. Short, concrete asks work best, such as "find the customer with this email in Zammad" rather than a long paragraph. Everything the agent does is limited to what your own Zammad account is allowed to do.

Does connecting Zammad give the AI access to my whole helpdesk?

No. Every request to Zammad runs as the person who signed in, so the agent sees only the customers, organizations, groups, and roles that person can already see in Zammad. Elaichi can narrow that further, for example to read-only or to specific actions, but it can never grant more than your Zammad permissions allow.

Can my team share one Zammad connection?

Yes. One administrator connects Zammad in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who looked up or changed a Zammad customer, organization, or role.

Can I stop an agent from deleting or changing things in Zammad?

Yes. In Elaichi you can block individual actions on the Zammad connector, such as deleting a user, deleting an organization, or editing roles, while leaving lookups and updates available. A blocked action is never shown to Claude, ChatGPT, or any other client, so no prompt, accidental or otherwise, can trigger it.

What happens to a Zammad connection when someone leaves?

When you offboard a person in Elaichi, their access to Zammad through every connected client ends immediately. If they were using a shared Zammad connection, it keeps working for everyone else on the team. If you want to remove Zammad entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Put Zammad in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.