Connector guide3-minute read13 MCP tools7 languages

Connect Zammad to Gemini CLI via MCP: Ticket Search

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 teamUpdated 3 min read Open-source on GitHub

No credit card · 7-day trial · Self-host alternative available

Zammad

Zammad

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

tools

13

Region

DE

Category

Customer Support

Authentication

API Key

Required env vars

ZAMMAD_URLZAMMAD_API_TOKEN
Install in one click on Cloud

7-day free trial · No credit card

  • 7-day free trial
    No credit card required
  • GDPR & SOC 2 ready
    EU data residency, audit logs
  • Open-source on GitHub
    Open source · AGPL-3.0
  • Works with ChatGPT, Claude, Gemini
    Any MCP-compatible client

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.

Guided setup

Connect Zammad to Gemini in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Zammad in the guided setup, then add your MCP URL to Gemini. No code and no server to run.

No credit card · 7-day trial · Self-host alternative available

Try asking

Example prompts for Zammad

Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.

Zammad · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Zammad, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

Zammad + Gemini

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.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

ZAMMAD_URL, ZAMMAD_API_TOKEN

Step 1 — Get credentials

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)

Step 2 — Install the adapter

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

Step 3 — Add the connector in Gemini

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Gemini CLI reads MCP servers from ~/.gemini/settings.json (or %APPDATA%\gemini\settings.json on Windows). Add:

{
  "mcpServers": {
    "anythingmcp": {
      "httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}
  1. Get your MCP API key from AnythingMCP → MCP Servers → your server → API keys.
  2. Save the file and restart gemini.
  3. Run /mcp inside the Gemini CLI — Zammad should be listed as available.
  4. Vertex AI Studio: pass https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID to the tools array of your request with the same X-API-Key header.

Available 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

FAQ

Does Gemini 1.5 Pro or 2.x support MCP? Yes — Gemini CLI ≥ 0.4 and Vertex AI tools API both accept MCP httpUrl connectors with custom headers.

Next steps

Was this guide helpful?

Connect Zammad to Gemini in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Zammad in the guided setup, then add your MCP URL to Gemini. No code and no server to run.

Related guides