Zammad MCP Server
Zammad ticket, user, and attachment management for AI agents via API.
Data last scanned today · Reviewed today
Overview
The Zammad MCP Server provides a direct interface for AI assistants to interact with Zammad helpdesk systems. Users can perform comprehensive ticket management, including searching, creating, and updating tickets, as well as managing associated comments, tags, and file attachments. Beyond ticket operations, the server facilitates user and organization management, allowing assistants to search and retrieve profile information. It also exposes system-level data like ticket states, priorities, and group lists, while offering pre-configured prompts for tasks such as ticket analysis and response drafting.
Our verdict
This server carries a high-risk score of 40/100, primarily due to the lack of a read-only mode, which grants the underlying integration full write access to your Zammad instance. Furthermore, as a community-maintained project that is not officially endorsed by Zammad GmbH, users should proceed with caution and verify the codebase before connecting it to production support environments.
- Zero direct dependencies reduce potential supply-chain vulnerabilities.
- Active development cycle with commits occurring as recently as today.
- Comprehensive toolset covering tickets, users, organizations, and file attachments.
- No read-only mode requires granting full write access by default.
- Community-maintained status lacks official endorsement or audit by Zammad.
- Authentication methods currently lack external verification or review.
Tools
| Tool | Description | Risk |
|---|---|---|
| zammad_search_tickets | Search tickets with multiple filters | low |
| zammad_get_ticket | Get detailed ticket information with articles (supports pagination) | low |
| zammad_create_ticket | Create new tickets | medium |
| zammad_update_ticket | Update ticket properties | medium |
| zammad_add_article | Add comments/notes to tickets | medium |
| zammad_add_ticket_tag | Manage ticket tags | medium |
| zammad_remove_ticket_tag | Manage ticket tags | medium |
| zammad_get_ticket_tags | Get tags assigned to a specific ticket | low |
| zammad_list_tags | List all tags defined in the system (requires admin.tag permission) | low |
| zammad_get_article_attachments | List attachments for a ticket article | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What authentication methods does the Zammad MCP server support?
The server supports authentication via Zammad API token, OAuth2 token, or standard username and password credentials.
›How do I configure the server to work with my self-signed TLS certificate?
You can set the ZAMMAD_INSECURE environment variable to a truthy value like true, 1, or yes to disable TLS certificate verification.
›Is it possible to use Docker secrets for managing my API token?
Yes, you can provide a token file path using the ZAMMAD_HTTP_TOKEN_FILE environment variable and mount the secret file into the container.
›Are there specific permissions required for certain tools?
Yes, using the zammad_list_tags tool requires admin.tag permission in Zammad.
›How are performance-heavy items like groups and ticket states handled?
The server caches data for groups, ticket states, and priority levels to ensure optimal performance.
›Does the server provide a way to access Zammad data directly without executing tools?
Yes, you can use the built-in URI-based resources to access specific tickets, user profiles, organization data, and ticket queues.
Badge
Maintain this server? Add the live badge to your README.