Labsco
QasperAI logo

Zammad

from QasperAI

A powerful, production-ready Model Context Protocol (MCP) server for Zammad - the open-source helpdesk and ticket system.

🔥🔥🔥✓ VerifiedAccount requiredNeeds API keys
#automation#database#devops#git#security#customer-support

Zammad MCP Server

The Zammad MCP Server is a free, open-source Model Context Protocol (MCP) server for Zammad. It connects Claude Desktop, Cursor, and other MCP clients to your Zammad helpdesk so AI agents can search tickets, summarize conversations, draft replies, and inspect users, organizations, groups, and system metadata through typed tools.

This page is the main documentation hub for the Zammad MCP server. Use it if you want to installzammad-mcp-server, connect it to Claude or Cursor, compare it with Zammad’s native AI features, or understand whether MCP is the right integration layer for your helpdesk automation.

  • License: MIT

  • Package: zammad-mcp-server on PyPI

  • Source: github.com/Softoft-Orga/zammad-mcp-server

  • Primary use case: external AI assistants working with Zammad via the Zammad REST API

  • Zammad compatibility: 6.0+ via REST API — see matrix below

Zammad version compatibility

The MCP package (zammad-mcp-server) is versioned independently from Zammad. One PyPI release works with every row below; point ZAMMAD_URL at your instance.

Zammad Status Notes 7.1 Tested (primary) Default in bundled Docker dev stack 7.0 Tested PostgreSQL required on Zammad side 6.5.x Compatible Last 6.x line 6.0 – 6.4.x Compatible Minimum supported major line < 6.0 Not supported

Local dev stack: clonezammad-mcp-server/docker, copy .env.example → .env, and set ZAMMAD_VERSION (7.1, 7.0, 6.5, or6.3). Full details: COMPATIBILITY.md on GitHub.

Use get_server_info after health_check to confirm the connected Zammad version.

Who is this for?

Role Typical use Zammad administrators Pilot AI on tickets without building a custom API integration Support leads Faster ticket lookup, summaries, and draft replies via Claude or Cursor AI / automation engineers Standard MCP tooling instead of one-off REST scripts Consultants Repeatable Zammad + MCP setup for client environments

How this fits the Zammad + AI landscape

flowchart LR
 subgraph native [Zammad 7.1 native AI]
 Z7[Summaries and writing assistant inside Zammad UI]
 end
 subgraph mcp [Zammad MCP Server]
 MCP[Claude Desktop Cursor custom agents]
 end
 subgraph otai [Open Ticket AI Runtime]
 RT[Custom trained models on-prem routing]
 end
 Zammad[(Zammad REST API)]
 Z7 --> Zammad
 MCP --> Zammad
 RT --> Zammad

  • Zammad 7.1 native AI — built-in summaries, writing assistant, and AI agents inside the Zammad UI.

  • Zammad MCP Server (this project) — connects external MCP clients (Claude Desktop, Cursor, your own agents) to Zammad.

  • Open Ticket AI Runtime — on-prem inference with custom-trained classification models via the OTAI Zammad connector plugin (see Zammad + OTAI integration).

All three can coexist. MCP is the fastest path to “talk to my helpdesk from Claude.”

What you can do with Zammad MCP

The Zammad MCP server exposes Zammad as structured tools instead of raw REST calls. Common workflows include:

Workflow MCP capability Triage open tickets Search tickets by state, group, customer, priority, or query Summarize long conversations Fetch ticket articles and run the built-in ticket summary prompt Draft support replies Generate customer communication drafts for human review Inspect customers Look up users and organizations connected to a ticket Audit agent access List enabled tools and deny destructive operations with environment variables Check system state Run health_check and inspect the connected Zammad version

Key features

  • 30+ MCP tools for tickets, articles, users, organizations, and groups

  • Access control via environment variables (category allow/deny, tool deny-list, group scope)

  • Multiple auth modes — API token (recommended), OAuth2, basic auth

  • Install options — pip, uvx, Docker, SSE transport for remote clients

  • Built-in prompts — ticket summary, customer communication, escalation analysis

  • Resource URIs — zammad://ticket/{id}, zammad://user/{id}, zammad://states

Documentation map

Page What you will learn Quick Start Install and run health_check in minutes Claude & Cursor Setup MCP client configuration Configuration Environment variables and access policies Tools Reference All MCP tools by category Security Tokens, least privilege, production checklist Deployment Docker, SSE, and production notes

Zammad MCP Server vs alternatives

Option Best fit Difference Zammad MCP Server Teams that want Claude, Cursor, or custom agents to work with Zammad External MCP clients, typed tools, API token based access control Zammad 7.1 native AI Teams that want AI assistance directly inside the Zammad UI Built into Zammad, but not a general MCP bridge for external agents Custom REST scripts One-off internal automations Flexible, but each script must handle auth, schemas, errors, and safety Open Ticket AI Runtime Production ticket classification and routing with private models Background automation with custom-trained models, not an interactive MCP client

Choose the Zammad MCP Server when the search intent is “connect my AI assistant to Zammad now.” Choose Open Ticket AI Runtime when you need autonomous queue routing, classification, or custom models trained on your historical ticket data.

Learn more

  • Tutorial: Zammad MCP Server — setup and usage (blog)

  • Repository: Softoft-Orga/zammad-mcp-server

  • Package: zammad-mcp-server on PyPI

Next steps

  • Follow the Quick Start guide.

  • Harden access with Security before production use.

  • Need custom models trained on your queues? Explore Open Ticket AI for Zammad.