MCP Server for Zammad API
If you already use Zammad, the zammad mcp server is the piece that lets your assistant work with it directly. MCP Server for Zammad API.
Resources allow the AI to read data from Zammad in a structured way using URIs.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Requires — title, group, customer (email or user ID), bodyOptional — type (article type, default: "note"), internal (boolean, default: false)user.reader — To view and search usersTools — Tools allow the AI to perform actions or specific queries within ZammadSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: ZAMMAD_URL, ZAMMAD_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Zammad's toolset — Requires, Optional, user.reader and 1 more — is a fair guide to whether it matches your workflow. It is maintained by arush15june; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Requires | title, group, customer (email or user ID), body. |
| Optional | type (article type, default: "note"), internal (boolean, default: false). |
| user.reader | To view and search users. |
| Tools | Tools allow the AI to perform actions or specific queries within Zammad. |
{
"mcpServers": {
"zammad": {
"command": "<path-to>/zammad-go-mcp.exe",
"args": [],
"env": {
"ZAMMAD_URL": "<zammad_url>",
"ZAMMAD_TOKEN": "<zammad_token>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ZAMMAD_URL | Endpoint or connection string the server talks to. | Yes |
| ZAMMAD_TOKEN | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.