Zammad MCP

A Model Context Protocol (MCP) server for Zammad integration, enabling AI assistants to interact with tickets, users, and organizations.

LLM Mart 0 views 5 listing impressions
Transport
Not stated
Package
—
Registry id
—

No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.

An MCP server that connects AI assistants to Zammad, providing tools for managing tickets, users, organizations, and attachments.

Disclaimer: This project is not affiliated with or endorsed by Zammad GmbH or the Zammad Foundation. This is an independent integration that uses the Zammad API.

Features

Tools

  • Ticket Management

    • zammad_search_tickets - Search tickets with multiple filters
    • zammad_get_ticket - Get detailed ticket information with articles (supports pagination); custom object attributes are included
    • zammad_create_ticket - Create new tickets
    • zammad_update_ticket - Update ticket properties, including custom object attributes via custom_fields
    • zammad_add_article - Add comments/notes to tickets
    • zammad_merge_tickets - Merge a ticket into another (irreversible)
    • zammad_add_ticket_tag / zammad_remove_ticket_tag - Manage ticket tags
    • zammad_bulk_update_tickets - Update, assign, tag, or close up to 100 tickets in one call with per-ticket failure reporting
    • zammad_get_ticket_tags - Get tags assigned to a specific ticket
    • zammad_list_tags - List all tags defined in the system (requires admin.tag permission)
    • zammad_export_tickets - Export tickets with their conversation articles to a JSONL file on the server host (requires ZAMMAD_EXPORT_DIR; see Ticket Export)
  • Attachment Support

    • zammad_get_article_attachments - List attachments for a ticket article
    • zammad_download_attachment - Download attachment content (base64-encoded)
  • User & Organization Management

    • zammad_create_user - Create a Zammad user
    • zammad_get_user / zammad_search_users - User information and search
    • zammad_get_organization / zammad_search_organizations - Organization data
    • zammad_get_current_user - Get authenticated user info
  • System Information

    • zammad_list_groups - Get all available groups (cached for performance)
    • zammad_list_ticket_states - Get all ticket states (cached for performance)
    • zammad_list_ticket_priorities - Get all priority levels (cached for performance)
    • zammad_get_ticket_stats - Get ticket statistics (optimized with pagination)
  • Webhook Events (HTTP transport only)

    • zammad_list_events - Poll ticket events delivered by Zammad webhooks (see Webhook Events)

Resources

Access Zammad data directly:

  • zammad://ticket/{id} - Individual ticket details
  • zammad://user/{id} - User profile information
  • zammad://organization/{id} - Organization details
  • zammad://queue/{group} - Ticket queue for a group

Prompts

Pre-configured prompts:

  • analyze_ticket - Comprehensive ticket analysis
  • draft_response - Generate ticket responses
  • escalation_summary - Summarize escalated tickets

Installation

Option 1: Run Directly with uvx (Recommended)

Run without installation:

# Install uv if you haven't already
# macOS/Linux:
curl -LsSf https://astral.sh/uv/install.sh | sh
# Windows:
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"

# Run directly from GitHub
uvx --from git+https://github.com/basher83/zammad-mcp.git mcp-zammad

# Or with environment variables
ZAMMAD_URL=https://your-instance.zammad.com/api/v1 \
ZAMMAD_HTTP_TOKEN=your-api-token \
uvx --from git+https://github.com/basher83/zammad-mcp.git mcp-zammad

Option 2: Docker Run

For production or containerized deployments:

# Basic usage with environment variables
docker run --rm -i \
  -e ZAMMAD_URL=https://your-instance.zammad.com/api/v1 \
  -e ZAMMAD_HTTP_TOKEN=your-api-token \
  ghcr.io/basher83/zammad-mcp:latest

# If you must skip TLS verification (self-signed / internal CA), add:
#   -e ZAMMAD_INSECURE=true

From the project's README.

Related servers

Let LLM help you achieve your regression analysis with Stata

18 views

vSphere with Tanzu (VKS): Namespace and TanzuKubernetesCluster lifecycle. Requires vSphere 8.x+.

17 views

Web search, deep research, prediction markets & crypto data for AI agents. Pay per call via x402.

16 views

MCP server for Geargrafx PC Engine / TurboGrafx-16 emulator

15 views