Zammad MCP connector
The Zammad connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- Connects with an API key
- Free 14-day trial
- No credit card
Show open tickets in the Support group this week.
Working in Zammad with Elaichi
-
Zammad users get me
-
List all Zammad users
-
Zammad users search
How to connect Zammad to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Zammad MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Zammad MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Zammad MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Zammad MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Zammad MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Zammad to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with Zammad through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Zammad is logged.
-
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.”
What connecting Zammad gets you
6 screens from Elaichi, each doing one job for your Zammad account.
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, Cursor or Microsoft Copilot
The agent
Ask about tickets, get real answers.
Type a question in plain language and read it from live Zammad records.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Zammad.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
98 Zammad tools ready to call.
Tickets, users, organizations and groups covered, with no custom code to write.
Toolboxes
Every team gets its own toolbox.
Curate Zammad tools per team so support, ops and billing see different sets.
Shared connections
Share a Zammad login, never the password.
Teammates work through a connection while the credential stays with whoever connected it.
Audit log
Every Zammad call is written down.
When, who, what happened, type and resource, in an append only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Zammad digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch tickets
Zammad
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Zammad
Queued
Automations
A schedule drafts your ticket digest.
Zammad tickets are fetched, grouped, drafted by an agent, approved, then posted back.
Zammad health
Refreshed 4 minutes ago · every 15 minutes · from the tickets collection
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%
Collections and dashboards
Helpdesk numbers arrive before anyone asks.
Four metrics, 14 days of tickets created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Zammad
All three can connect Zammad to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Zammad tools | Allow or restrict single Zammad tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Zammad call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 I stop an agent from deleting or changing things in Zammad?
Yes. In Elaichi you can restrict individual actions on the Zammad connector, such as deleting a user, deleting an organization, or editing roles, while leaving lookups and updates available. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client at the same time.
Does the Zammad MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Zammad is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Zammad?
Yes. Both let Claude, ChatGPT or Cursor use Zammad. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Zammad call.
How is Elaichi different from Composio for Zammad?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Zammad: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Zammad in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot