AnythingMCP Cloud is live — 7-day free trial−30% for 3 months with START30
AnythingMCP
Connector guide5-minute read13 MCP tools7 languages

Connect Zammad to Microsoft Copilot via MCP

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, plus full-text search across the ticket base. REST API v1 on your own Zammad instance, token auth.

HCBy HelpCode teamUpdated 5 min read Open-source on GitHub
Install Zammad on Cloud — free trialRead the step-by-step guide

No credit card · 7-day trial · Self-host alternative available

Zammad

Zammad

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, full-text search across the ticket base, and ticket updates and merges. REST API v1 on your own Zammad instance, token auth.

tools

13

Region

DE

Category

Customer Support

Authentication

API Key

Required env vars

ZAMMAD_URLZAMMAD_API_TOKEN
Install in one click on Cloud

7-day free trial · No credit card

  • 7-day free trial
    No credit card required
  • GDPR & SOC 2 ready
    EU data residency, audit logs
  • Open-source on GitHub
    Open source · AGPL-3.0
  • Works with ChatGPT, Claude, Gemini
    Any MCP-compatible client

Summary

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, plus full-text search across the ticket base. REST API v1 on your own Zammad instance, token auth.

Guided setup

Connect Zammad to Microsoft Copilot in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Zammad in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.

Set up Zammad freeI already have an account

No credit card · 7-day trial · Self-host alternative available

Try asking

Example prompts for Zammad

Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.

Zammad · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Zammad, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

Zammad + Microsoft Copilot

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, plus full-text search across the ticket base. REST API v1 on your own Zammad instance, token auth.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

ZAMMAD_URL, ZAMMAD_API_TOKEN

Step 1 — Get credentials

Getting a token

  1. Sign in to Zammad, open your avatar → Profile → Token Access, and switch token access on if an admin has not already.
  2. Create a token with the permissions the agent needs — ticket.agent to read and answer tickets, admin only if you really want the agent to change configuration.
  3. Put it in ZAMMAD_API_TOKEN and your instance's base URL (no trailing slash, no /api) in ZAMMAD_URL.

The Authorization header is Token token=…, Zammad's own scheme — not Bearer. This adapter sends it correctly; it is the first thing to check when hand-building a Zammad connector that 401s with a token you know is good.

…(continued in the in-app connector instructions)

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

  1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
  2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
  3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
  4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
  5. Try it in the agent's Test pane: ask for something that needs the Zammad tools.
  6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

ToolWhat it does
zammad_get_meRead the user the token belongs to, with their roles, group memberships and permissions
zammad_list_ticketsList tickets, newest first, with state, priority, group, owner and customer
zammad_search_ticketsFull-text search across tickets
zammad_get_ticketRead one ticket by number or id with all its attributes: state, priority, owner, customer, group, SLA and custom fields
zammad_list_ticket_articlesRead the conversation on one ticket: every article in order, with sender, type, body and whether it is internal
zammad_list_usersList users (agents and customers) with their name, e-mail, organization and active flag
zammad_search_usersFind a user by name, e-mail or phone fragment — the usual first step before opening a ticket for somebody
zammad_list_organizationsList organizations (the customer companies tickets are grouped under) with their domain, note and VIP flag
zammad_list_groupsList the groups (queues) tickets are routed into, with their assignment and follow-up settings
zammad_create_ticketOpen a real ticket in the live instance
zammad_add_articleAdd an article to an existing ticket

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

Was this guide helpful?

Connect Zammad to Microsoft Copilot in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Zammad in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.

Set up Zammad freeSelf-host with DockerContact Sales

Related guides

Connectors

Connect Zammad to Meta Muse via MCP: Tickets and Users

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, plus full-text search across the ticket base. REST API v1 on your own Zammad instance, token auth.

Connectors

Connect Zammad to ChatGPT via MCP: Tickets and Replies

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, plus full-text search across the ticket base. REST API v1 on your own Zammad instance, token auth.

Connectors

Connect Zammad to Claude via MCP: Tickets and Replies

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, plus full-text search across the ticket base. REST API v1 on your own Zammad instance, token auth.

Connectors

Connect Zammad to Cursor via MCP: Tickets and Users

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, plus full-text search across the ticket base. REST API v1 on your own Zammad instance, token auth.

Connectors

Connect Zammad to Gemini CLI via MCP: Ticket Search

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, plus full-text search across the ticket base. REST API v1 on your own Zammad instance, token auth.

Connectors

Zammad MCP Server: Tickets, Users and Groups

Zammad open-source helpdesk: tickets, their articles, users, organizations and groups, plus full-text search across the ticket base. REST API v1 on your own Zammad instance, token auth.