Zammad MCP Server — Claude & Cursor Setup

Configure Claude Desktop and Cursor to use the Zammad MCP Server via uvx or a local install — with screenshots for the Zammad token flow.

Claude & Cursor Setup

Both Claude Desktop and Cursor support MCP servers that run as local subprocesses (stdio transport). You need two things before editing MCP config:

1. A Zammad personal access token — walkthrough with screenshots in Quick Start → Create a Zammad API token
2. Your Zammad base URL (https://helpdesk.example.com)

Cursor — step by step

1. Open Cursor Settings (gear icon) → MCP (or Features → MCP depending on your Cursor version).
2. Click Add MCP server or edit the JSON config file Cursor shows.
3. Paste the configuration below. Replace ZAMMAD_URL and ZAMMAD_HTTP_TOKEN with your values.
4. Save and reload MCP servers (or restart Cursor).
5. Open a chat and ask: “Run health_check on Zammad.”
6. Optional: “Call get_allowed_tools and list enabled tools.”

Example configuration:

{
  "mcpServers": {
    "zammad": {
      "command": "uvx",
      "args": ["zammad-mcp-server"],
      "env": {
        "ZAMMAD_URL": "https://your-zammad-instance.example.com",
        "ZAMMAD_HTTP_TOKEN": "your_token",
        "MCP_DENIED_TOOLS": "delete_ticket,delete_user,delete_organization"
      }
    }
  }
}

Pin the package version in production configs:

"args": ["zammad-mcp-server==0.2.0"]

Using a local venv instead of uvx:

{
  "mcpServers": {
    "zammad": {
      "command": "C:\\path\\to\\.venv\\Scripts\\zammad-mcp-server.exe",
      "env": {
        "ZAMMAD_URL": "https://your-zammad-instance.example.com",
        "ZAMMAD_HTTP_TOKEN": "your_token"
      }
    }
  }
}

On macOS/Linux, point command to the zammad-mcp-server binary inside your virtualenv.

Zammad token screenshots (Cursor setup uses the same token)

Paste the copied value into the ZAMMAD_HTTP_TOKEN field in Cursor’s MCP config.

Claude Desktop

Config file locations:

Use the same JSON structure as the Cursor example above. Restart Claude Desktop after saving.

Zammad 7.1.x notes

The MCP server uses the Zammad REST API only — no Zammad-side plugin is required.

After connecting, run get_server_info to confirm the Zammad version the token sees.

Local Zammad (Docker dev stack)

If you use the docker-compose dev environment:

"env": {
  "ZAMMAD_URL": "http://localhost:8080",
  "ZAMMAD_HTTP_TOKEN": "your_dev_token"
}

Default admin credentials in the dev stack are documented in the GitHub README — change them before exposing the instance.

Example workflows

Once connected, you can ask your assistant to:

• Search and summarize long ticket threads
• Draft customer-facing replies (you review before create_article)
• List organizations or users matching criteria
• Report ticket stats for a date range

Always review AI-generated ticket updates before applying them in production.

Troubleshooting

Security reminder

• Never commit tokens into git-tracked config files.
• Prefer MCP_DENIED_TOOLS for delete operations in agent-facing setups.
• See Configuration for role-based policy recipes and Security for production checklists.