Zammad Mcp Server

MCPAI代理

提供方 Softoft-Orga · 包名 zammad-mcp-server

AI代理 stdio · 本地进程 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorCodex
查看接入方式

A production-ready Model Context Protocol (MCP) server for Zammad, the open-source helpdesk and ticket system. It gives Claude, Cursor, and other MCP clients structured access to tickets, users, organizations, groups, and system metadata with configurable access control.

一句话选型结论

按资料字段整理

Zammad Mcp Server 属于AI代理类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

mcp helpdesk tickets customer support ai agents claude cursor python

支持客户端

适用场景

mcphelpdesktickets

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
uvx zammad-mcp-server

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Cross-platform,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zammad Mcp Server当前 未标注 stdio · 本地进程 本地部署 有 未标注
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Softoft-Orga上游标注的维护方 Softoft-Orga
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时zammad-mcp-server · Cross-platform本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

19.8 KB
来自项目仓库与上游目录的原文,未做删改

Zammad MCP Server — Connect Claude, Cursor & LLMs to Your Zammad Helpdesk

Zammad MCP Server is a free, open-source, production-ready Model Context Protocol (MCP) server for Zammad, the open-source helpdesk and ticket system. It connects AI assistants — Claude Desktop, Cursor, and any MCP-compatible LLM agent — directly to your Zammad instance, so you can search tickets, summarize threads, draft replies, and manage users and organizations in natural language.

> In one line: uvx zammad-mcp-server turns your Zammad helpdesk into a set of typed tools any AI agent can call — no Zammad plugin, no custom REST glue code.

> ⭐ Find this useful? Star the repo — it helps other Zammad teams discover the project and shapes the roadmap.

Table of Contents

  • Overview
  • Why use the Zammad MCP Server?
  • Key features
  • Zammad compatibility
  • Documentation
  • Quick start
  • Zammad Commander (browser chat UI)
  • Available MCP tools
  • Access control & security
  • Authentication methods
  • Architecture
  • Hosting & deployment options
  • FAQ
  • Contributing
  • License

Overview

The Zammad MCP Server gives AI assistants like Claude structured, type-safe access to Zammad ticket system functionality over the Model Context Protocol — an open standard for connecting LLMs to external tools and data. Instead of scraping the UI or pasting ticket text into a chat window, the assistant calls discrete, validated tools (search_tickets, get_ticket_articles, create_article, and 30+ more) and gets clean, schema-checked data back.

This enables AI-powered ticket management, customer-support automation, and helpdesk reporting through natural-language interactions — while keeping your data on your Zammad instance and your MCP client.

Why use the Zammad MCP Server?

Connecting a large language model to a real helpdesk usually means writing a bespoke Zammad REST integration, handling authentication, and reinventing access control before you get a single useful answer. This server removes that friction:

  • Talk to your helpdesk from Claude or Cursor — "Summarize ticket 4821", "List open tickets in the Support queue", "Draft a reply to this customer."
  • Triage and reporting — let an agent classify, prioritize, and summarize incoming tickets, or pull get_ticket_stats for analytics.
  • Safe by default — granular, environment-driven access control lets you ship read-only or deny destructive tools (delete_ticket, delete_user) in production.
  • One integration, every client — write to MCP once and it works across Claude Desktop, Cursor, and custom agent stacks.
  • No vendor lock-in — MIT-licensed, self-hosted, and works with any Zammad 6.0+ / 7.x instance via the REST API (no Zammad-side plugin required).

Key features

  • Comprehensive API Coverage: Full access to tickets, users, organizations, groups, and more
  • Advanced Access Control: Granular permissions with category-based and tool-level restrictions
  • Production-Ready: Built with FastMCP, Pydantic, and modern Python practices
  • Flexible Authentication: Supports API tokens, OAuth2, and basic authentication
  • Smart Caching: Intelligent caching for static data (groups, states, priorities)
  • Type-Safe: Full Pydantic models with runtime validation
  • Extensible: Easy to add new tools and integrations
  • Well-Tested: Comprehensive test suite with 90%+ coverage

Zammad compatibility

The MCP server talks to Zammad through the REST API. No Zammad-side plugin is
required. Full matrix: docs/COMPATIBILITY.md.

Zammad version Status
7.1 Tested (primary; default dev stack)
7.0 Tested
6.5.x Compatible
6.0 – 6.4.x Compatible (minimum supported line)
< 6.0 Not supported

MCP package vs Zammad: zammad-mcp-server on PyPI is versioned independently
(0.1.x). One MCP release works with every supported Zammad version — set
ZAMMAD_URL to your instance; no per-Zammad MCP build.

Local dev stack: docker/ ships Zammad 7.1 by default. Override with
ZAMMAD_VERSION in docker/.env (7.0, 6.5, 6.3 also supported). See
docker/README.md.

Zammad 7.x requires PostgreSQL on the Zammad side (MySQL is not supported
from 7.0 onward). The bundled dev stack uses PostgreSQL.

Documentation

Full guides, security checklists, and deployment notes live on the Open Ticket AI website:

Page What you will learn
Zammad MCP Server (overview) Who it is for and how it fits the Zammad + AI landscape
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 compatibility (GitHub) Supported Zammad versions and dev-stack tags
Zammad Commander (GitHub) LibreChat + MCP + your Zammad — internal admin chat

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

Deutsch: Zammad MCP Server Dokumentation · Einrichtung und Nutzung (Blog)

How this fits the Zammad + AI landscape

  • Zammad 7.1 native AI — built-in summaries and writing assistant inside the Zammad UI.
  • Zammad MCP Server (this project) — connects external MCP clients (Claude Desktop, Cursor, custom agents) to Zammad.
  • Zammad Commander — browser chat UI (LibreChat + this MCP server + your Zammad). No Cursor required; docker compose up for internal admin chat. See Zammad Commander (browser chat UI).
  • Open Ticket AI Runtime — on-prem inference with custom-trained models via the OTAI Zammad connector (integration guide).

All three can coexist. MCP is the fastest path to “talk to my helpdesk from Claude.” Want a team chat UI instead of an IDE? Use Zammad Commander. Need custom models on your queues? See Open Ticket AI for Zammad.

Quick Start

> Step-by-step walkthrough: Quick Start guide

Installation

From PyPI (recommended for MCP clients):```bash
pip install zammad-mcp-server

or

uv tool install zammad-mcp-server

or run once without installing

uvx zammad-mcp-server


**From source (development):**```bash
git clone https://github.com/Softoft-Orga/zammad-mcp-server.git
cd zammad-mcp-server
uv sync --extra dev

Configuration

See the Configuration guide for all environment variables and access policies.

Create a .env file:```env
ZAMMAD_URL=https://your-zammad-instance.com
ZAMMAD_HTTP_TOKEN=your_api_token_here

Optional: Access control

MCP_ALLOWED_CATEGORIES=all
MCP_DENIED_TOOLS=delete_ticket,delete_user


### Running the Server```bash
# Run with stdio transport (for Claude Desktop)
zammad-mcp-server

# Run with Streamable HTTP (Docker / remote clients; recommended)
zammad-mcp-server --transport http --host 0.0.0.0 --port 8000

# Legacy SSE transport (older MCP clients)
zammad-mcp-server --transport sse --host 0.0.0.0 --port 8000

Claude Desktop / Cursor

Full client setup: Claude & Cursor Setup

Add to claude_desktop_config.json or Cursor Settings → MCP:```json
{
"mcpServers": {
"zammad": {
"command": "uvx",
"args": ["zammad-mcp-server"],
"env": {
"ZAMMAD_URL": "https://your-zammad-instance.com",
"ZAMMAD_HTTP_TOKEN": "your_token",
"MCP_DENIED_TOOLS": "delete_ticket,delete_user,delete_organization"
}
}
}
}


Restart the app after saving. Ask: _&quot;Run health_check on Zammad&quot;_ or _&quot;List open tickets.&quot;_

## Zammad Commander (browser chat UI)

Not every agent wants Cursor or Claude Desktop. **Zammad Commander**
is the official companion project: Docker Compose bundles **LibreChat**, **this MCP server**
(Streamable HTTP sidecar), and **your Zammad** so support leads get a browser chat for
search, summaries, and reply drafts (human-in-the-loop — no auto-send, deletes denied by default).```bash
git clone https://github.com/Softoft-Orga/zammad-commander.git
cd zammad-commander
cp env.example .env
# Set ZAMMAD_URL, ZAMMAD_HTTP_TOKEN, and LibreChat secrets.

docker compose up -d
# On-prem LLM: add -f docker-compose.onprem.yml (see Commander README).

Open http://localhost:3080, pick Zammad Commander, and start chatting.

You need Where
Full setup (OpenRouter vs Ollama, demo Zammad, hardware) Commander README
Step-by-step from the MCP side docs/ZAMMAD_COMMANDER.md
MCP env / deny lists Commander uses Configuration guide

Development Environment

We provide a complete Docker Compose setup for local development. Default: Zammad
7.1; set ZAMMAD_VERSION in docker/.env for other supported tags — see
docker/README.md.```bash
cd docker
docker-compose up -d

Wait for services to start (may take 2-3 minutes)

docker-compose ps

Access Zammad at http://localhost:8080

Default credentials: admin@example.com / admin


### Running Tests```bash
# Run all tests
pytest

# Run with coverage
pytest --cov=zammad_mcp_server --cov-report=html

# Run specific test file
pytest tests/test_models.py -v

Available MCP tools

The server provides 35 typed MCP tools for Zammad. Full reference: Tools Reference

Tickets

  • get_ticket - Get ticket details
  • search_tickets - Search with filters
  • create_ticket - Create new tickets
  • update_ticket - Update ticket properties
  • delete_ticket - Delete tickets (admin)
  • get_ticket_articles - Get all messages
  • create_article - Add responses/notes
  • get_ticket_stats - Analytics and metrics
  • get_ticket_states - List available states
  • get_priorities - List priority levels
  • list_ticket_tags / add_ticket_tag / remove_ticket_tag - Ticket tags
  • get_article_attachment - Download an article file
  • link_tickets / merge_tickets - Relate or merge tickets
  • summarize_ticket - Plain-text thread + tags for agents

Users

  • get_user - Get user details
  • search_users - Find users
  • create_user - Add new users
  • update_user - Modify user properties
  • delete_user - Remove users (admin)
  • get_current_user - Get authenticated user

Organizations

  • get_organization - Get organization details
  • search_organizations - Find organizations
  • create_organization - Add organizations
  • update_organization - Modify organizations
  • delete_organization - Remove organizations (admin)

Groups

  • get_group - Get group details
  • list_groups - List all groups
  • create_group - Create a group

Tags (admin catalog)

  • list_tags - Global tag list

System

  • health_check - Check server health
  • get_server_info - Get Zammad version/info
  • get_allowed_tools - List accessible tools

Access control & security

The server includes a sophisticated access control system so you can safely connect AI agents to production Zammad. Production checklist: Security guide

Permission Levels

  • DENIED - Tool completely inaccessible
  • READ_ONLY - Can view but not modify
  • WRITE - Can read and modify data
  • ADMIN - Full access including deletion

Configuration via Environment Variables```env

Allow all categories (default)

MCP_ALLOWED_CATEGORIES=all

Allow specific categories only

MCP_ALLOWED_CATEGORIES=tickets,groups,system

Deny specific dangerous tools

MCP_DENIED_TOOLS=delete_ticket,delete_user,delete_organization

Restrict to specific groups (reads and writes)

MCP_ALLOWED_GROUPS=Support,Sales

Restrict to organization IDs

MCP_ALLOWED_ORGANIZATIONS=1,2

Read-only preset (no creates/updates/deletes)

MCP_DEFAULT_PERMISSION=read_only

Rate limit (0 disables)

MCP_RATE_LIMIT_PER_MINUTE=60


### Programmatic Access Control```python
from zammad_mcp_server.access_control import AccessController, AccessPolicy, Permission, ToolCategory

# Create custom policy
policy = AccessPolicy(
    default_permission=Permission.READ_ONLY,
    category_permissions={
        ToolCategory.TICKETS: Permission.WRITE,
        ToolCategory.ADMIN: Permission.DENIED,
    },
    denied_tools={&quot;delete_ticket&quot;},
)

controller = AccessController(policy)

Architecture

See ARCHITECTURE.md for detailed technical documentation.```
┌─────────────────┐ ┌─────────────────┐
│ Claude/AI │ │ MCP Client │
│ Assistant │────▶│ (Claude App) │
└─────────────────┘ └────────┬────────┘
│ MCP Protocol
┌────────▼────────┐
│ MCP Server │
│ (FastMCP) │
├─────────────────┤
│ Access Control │
│ Tools │
│ Resources │
└────────┬────────┘
│ HTTP/REST
┌────────▼────────┐
│ Zammad Client │
│ Wrapper │
└────────┬────────┘
│
┌────────▼────────┐
│ Zammad API │
│ Instance │
└─────────────────┘


## Authentication Methods

The server supports three authentication methods. Details: Configuration — authentication

### 1. API Token (Recommended)```env
ZAMMAD_HTTP_TOKEN=your_token_here

Create tokens in Zammad: Profile → Token Access

2. OAuth2 Token```env

ZAMMAD_OAUTH2_TOKEN=your_oauth_token


### 3. Username/Password```env
ZAMMAD_USERNAME=admin@example.com
ZAMMAD_PASSWORD=your_password

Resources

The server exposes several MCP resources:

  • zammad://ticket/{id} - Formatted ticket with articles
  • zammad://user/{id} - User details
  • zammad://config/states - Available ticket states
  • zammad://config/priorities - Available priorities
  • zammad://organization/{id} - Organization snapshot

Prompts

Built-in prompts for common workflows:

  • ticket_summary_prompt - Generate ticket summaries
  • customer_communication_prompt - Draft customer responses
  • escalation_analysis_prompt - Analyze escalation needs
  • analyze_ticket - Structured analysis with tags and SLA hints
  • draft_response - Locale-aware customer or internal reply
  • triage_queue - Prioritize open tickets in a group
  • escalation_summary - Overdue / pending-close briefing

Hosting options

The Zammad MCP Server can be hosted in multiple ways:

1. Local Development```bash

zammad-mcp-server


### 2. Docker Container

Published images are on **GitHub Container Registry** (`ghcr.io`):```bash
docker pull ghcr.io/softoft-orga/zammad-mcp-server:latest

docker run -p 8000:8000 \
  -e ZAMMAD_URL=https://your-zammad.com \
  -e ZAMMAD_HTTP_TOKEN=your_token \
  ghcr.io/softoft-orga/zammad-mcp-server:latest

# Override to legacy SSE if needed:
# docker run ... ghcr.io/softoft-orga/zammad-mcp-server:latest \
#   zammad-mcp-server --transport sse --host 0.0.0.0 --port 8000

Build locally:bash docker build -t zammad-mcp-server . docker run -p 8000:8000 -e ZAMMAD_URL=$ZAMMAD_URL zammad-mcp-server

3. Cloud Deployment

See the Deployment guide for Docker, SSE, and production hosting (Google Cloud Run, Railway, Fly.io, and more).

FAQ

What is the Zammad MCP Server?

It is an open-source Model Context Protocol server that exposes your Zammad helpdesk as typed tools for AI assistants. Any MCP client (Claude Desktop, Cursor, or a custom agent) can then read and act on Zammad tickets, users, and organizations in natural language.

How do I connect Claude or Cursor to Zammad?

Install the package and add it to your MCP client config with ZAMMAD_URL and ZAMMAD_HTTP_TOKEN. The fastest path is uvx zammad-mcp-server — see Quick start and the Claude & Cursor setup guide.

Which Zammad versions are supported?

Zammad 7.1 (primary, tested), 7.0 (tested), and 6.0–6.5.x (compatible). It talks to Zammad over the REST API, so no Zammad-side plugin is required. See the compatibility matrix.

Is it safe to use on a production Zammad instance?

Yes. Access is controlled by environment variables — restrict categories (MCP_ALLOWED_CATEGORIES), deny destructive tools (MCP_DENIED_TOOLS=delete_ticket,delete_user), or run fully read-only. Follow the Security guide before going live.

Is the Zammad MCP Server free and open source?

Yes — it is MIT-licensed and free to self-host. There is no SaaS dependency; your ticket data stays on your Zammad instance and your MCP client.

How is this different from Zammad's built-in AI?

Zammad 7.1's native AI adds summaries and a writing assistant inside the Zammad UI. The Zammad MCP Server instead connects external AI agents to Zammad. See how it fits the Zammad + AI landscape.

Can I run it with Docker?

Yes — see Hosting options and the Deployment guide for Docker, SSE, and cloud hosting (Cloud Run, Railway, Fly.io).

What is Zammad Commander?

Zammad Commander is a separate MIT
project: LibreChat + this MCP server + your Zammad in one docker compose up. Use it when
support leads need a browser chat UI instead of Claude Desktop or Cursor. Setup:
docs/ZAMMAD_COMMANDER.md.

Contributing

We welcome contributions! Please see CONTRIBUTING.md for guidelines.

Development Workflow

  1. Fork the repository
  2. Create a feature branch (git checkout -b feature/amazing-feature)
  3. Make your changes
  4. Run tests (pytest)
  5. Commit (git commit -m &#x27;Add amazing feature&#x27;)
  6. Push (git push origin feature/amazing-feature)
  7. Open a Pull Request

Roadmap

  • [ ] WebSocket support for real-time updates
  • [ ] Ticket subscription and notification system
  • [ ] Advanced search with Elasticsearch integration
  • [ ] Multi-tenant support
  • [ ] Audit logging
  • [ ] Custom tool plugins
  • [ ] GraphQL API support
  • [ ] Webhook integration

License

This project is licensed under the MIT License - see LICENSE for details.

Support

  • 📖 Documentation (EN) · Dokumentation (DE)
  • 📘 Setup tutorial (blog)
  • 🐛 Issue Tracker
  • 💬 Discussions

Acknowledgments

  • Built with FastMCP by James Lowin
  • Inspired by the Model Context Protocol
  • Zammad - The amazing open-source helpdesk

Related Projects

  • Zammad Commander — LibreChat + this MCP server + your Zammad (MIT, Docker Compose)
  • Zammad - The ticket system itself
  • zammad-py - Python client library

Made with ❤️ by Open Ticket AI

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Zammad Mcp Server 怎么安装?

在客户端按下面的安装命令接入:uvx zammad-mcp-server。对应的包名是 zammad-mcp-server。装完在客户端配置里引用同一个包或端点。

Zammad Mcp Server 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Zammad Mcp Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zammad Mcp Server 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Zammad Mcp Server 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Zammad Mcp Server 能提供哪些能力?

资料显示能力标签包括 mcp、helpdesk、tickets、customer support、ai agents、claude。具体工具清单以官方文档为准。

Zammad Mcp Server 需要什么运行环境?

运行时为 Cross-platform;属于本地进程,需要在本机装好运行环境。

Zammad Mcp Server 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。