MCP.so
Sign In
Servers

zammad-go-mcp

@arush15june

MCP Server for Zammad API

Overview

What is zammad-go-mcp?

A Go-based MCP server that connects AI assistants to the Zammad ticketing and customer support system via its REST API. It allows reading, searching, creating, and updating tickets and users, and retrieving communication history on tickets.

How to use zammad-go-mcp?

Clone the repository, build the binary with go build -o zammad-go-mcp main.go (requires Go 1.24+), then configure the server in an MCP client (e.g., Claude Desktop) by setting the command to the binary path and providing ZAMMAD_URL and ZAMMAD_TOKEN environment variables. The token must be generated in Zammad with appropriate permissions (e.g., ticket.agent, user.reader).

Key features of zammad-go-mcp

  • Exposes Zammad tickets and users as MCP resources
  • Provides tools to create, search, and update tickets
  • Supports adding internal or public notes to tickets
  • Allows searching users by email, login, or name
  • Retrieves full article (communication) history per ticket
  • Authenticates via a Zammad API token

Use cases of zammad-go-mcp

  • An AI assistant helping support agents view and manage their ticket queue
  • Automatically creating new tickets from external chat or email summaries
  • Looking up a customer’s details and ticket history during a conversation
  • Adding internal notes to tickets based on AI‑analyzed trends

FAQ from zammad-go-mcp

What permissions does the Zammad API token need?

At minimum ticket.agent (or ticket.customer) to view/create/search tickets and add articles, and user.reader to view/search users. Broader permissions may be required for future additions.

Where does the server run and how is it configured?

It runs as a local binary, configured via the ZAMMAD_URL and ZAMMAD_TOKEN environment variables. No external daemon or database is needed.

What transport does the server use?

The server uses the standard MCP protocol (stdio transport) as configured in the MCP client’s mcpServers block.

What are the runtime requirements?

Go version 1.24 or higher to build from source, and a running Zammad instance with a valid API token.

More from Other