Connector guide2-minute read11 MCP toolsEN · DE · IT

Zammad zu MCP — Zammad aus jedem KI-Agent steuern

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, plus full-text search across the ticket base. REST API v1 on your own Zammad instance, token auth.

HCBy HelpCode teamAktualisiert 2 min read Open Source auf GitHub

Keine Kreditkarte · 7 Tage Test · Self-Hosting-Alternative verfügbar

Zammad

Zammad

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, plus full-text search across the ticket base. REST API v1 on your own Zammad instance, token auth.

Tools

11

Region

DE

Kategorie

Customer Support

Authentifizierung

API Key

Benötigte Env-Vars

ZAMMAD_URLZAMMAD_API_TOKEN
Mit einem Klick in der Cloud installieren

7 Tage kostenlos testen · Keine Kreditkarte

  • 7 Tage kostenlos
    Keine Kreditkarte nötig
  • GDPR & SOC 2 ready
    EU-Datenhaltung, Audit-Logs
  • Open Source auf GitHub
    Open-Source · AGPL-3.0
  • Funktioniert mit ChatGPT, Claude, Gemini
    Jeder MCP-kompatible Client

Installation überspringen. In unter 2 Minuten einsatzbereit.

Starte eine kostenlose Testphase auf cloud.anythingmcp.com, füge Zammad mit einem Klick hinzu und richte deinen KI-Client (Claude, ChatGPT, Copilot oder Cursor) auf den erzeugten MCP-Endpoint. Kein Docker, kein git clone, keinerlei Entwicklungserfahrung nötig.

Kostenlos testen

Summary

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, plus full-text search across the ticket base. REST API v1 on your own Zammad instance, token auth.

Frag einfach

Beispiel-Prompts für Zammad

Klick auf einen Prompt, um ihn zu kopieren. In Claude, ChatGPT, Cursor, Gemini, Copilot oder OpenClaw einfügen — und gegen diesen Connector laufen lassen.

Zammad · live via MCP
Teilen
Opus 4.7

Claude ist KI und kann Fehler machen. Bitte Antworten gegenprüfen.

💡 Keine Installation? Nutze cloud.anythingmcp.com direkt. Einloggen, Connectors → Zammad klicken, Zugangsdaten einfügen, MCP-API-Key erzeugen — fertig. Kein Docker, kein git clone, kein lokaler Server.

Zammad

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, plus full-text search across the ticket base. REST API v1 on your own Zammad instance, token auth.

Einrichtung

Getting a token

  1. Sign in to Zammad, open your avatar → Profile → Token Access, and switch token access on if an admin has not already.
  2. Create a token with the permissions the agent needs — ticket.agent to read and answer tickets, admin only if you really want the agent to change configuration.
  3. Put it in ZAMMAD_API_TOKEN and your instance's base URL (no trailing slash, no /api) in ZAMMAD_URL.

The Authorization header is Token token=…, Zammad's own scheme — not Bearer. This adapter sends it correctly; it is the first thing to check when hand-building a Zammad connector that 401s with a token you know is good.

…(continued in the in-app connector instructions)

Voraussetzungen: ZAMMAD_URL, ZAMMAD_API_TOKEN

Connector lokal installieren

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Öffne http://localhost:3000/connectors/store, wähle Zammad und trage die unter Voraussetzungen aufgelisteten Variablen ein.

Verfügbare Tools

ToolWhat it does
zammad_get_meRead the user the token belongs to, with their roles, group memberships and permissions
zammad_list_ticketsList tickets, newest first, with state, priority, group, owner and customer
zammad_search_ticketsFull-text search across tickets
zammad_get_ticketRead one ticket by number or id with all its attributes: state, priority, owner, customer, group, SLA and custom fields
zammad_list_ticket_articlesRead the conversation on one ticket: every article in order, with sender, type, body and whether it is internal
zammad_list_usersList users (agents and customers) with their name, e-mail, organization and active flag
zammad_search_usersFind a user by name, e-mail or phone fragment — the usual first step before opening a ticket for somebody
zammad_list_organizationsList organizations (the customer companies tickets are grouped under) with their domain, note and VIP flag
zammad_list_groupsList the groups (queues) tickets are routed into, with their assignment and follow-up settings
zammad_create_ticketOpen a real ticket in the live instance
zammad_add_articleAdd an article to an existing ticket

Nächste Schritte

War dieser Guide hilfreich?

Your Zammad agent is one click away.

Install the connector, paste the key, prompt any MCP client. Free for 7 days, no credit card.

Verwandte Anleitungen