Context7
by upstash
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Computer or cloud★ 64,224MITUpdated today
Install
Zammad MCP
Overview
Description from the maker (original English)
Every Zammad ticket, article, and Knowledge Base operation as one CLI and MCP server - plus a
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Search & AI memory
- You need to fill in: ZAMMAD_API_TOKEN, ZAMMAD_URL, ZAMMAD_MCP_HTTP_TOKEN
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
ZAMMAD_API_TOKEN,ZAMMAD_BASE_URL,ZAMMAD_URL,ZAMMAD_MCP_HTTP_TOKEN,ZAMMAD_USER_AGENT,PRINTING_PRESS_CLIENT_PROFILE,ZAMMAD_MCP_READ_ONLY,ZAMMAD_NO_LOCAL_DATA
Values marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Set the ZAMMAD_API_TOKEN credential for the Zammad MCP server.
ZAMMAD_BASE_URLenvExplicit full API base, e.g. https://support.example.com/api/v1. Overrides the instance URL above. Leave blank unless your instance serves the API somewhere non-standard.- Root URL of your Zammad instance, e.g. https://support.example.com. The CLI appends /api/v1 itself. Without it the CLI points at a placeholder host that is not your instance.
- Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
ZAMMAD_USER_AGENTenvOverrides the User-Agent the CLI sends on Zammad requests. Leave blank to use the CLI's own built-in User-Agent.PRINTING_PRESS_CLIENT_PROFILEenvBinds this MCP server to one tenant-gated client profile. Leave blank to use the default client profile.ZAMMAD_MCP_READ_ONLYenvOptional. Set to exactly 1 to expose only read-only tools and refuse any state-changing call.ZAMMAD_NO_LOCAL_DATAenvOptional. Set to 1 to keep no local copy of API responses: reads go to the API and the response cache is off.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account servosity, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Search & AI memoryi
- More stars than 0% of the other 7247 servers in this category
- Published to the registry more recently than 96% of the other 7247 servers in this category
- Basic checks equal to or better than 100% of the other 7247 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Zammad MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: ZAMMAD_API_TOKEN, ZAMMAD_URL, ZAMMAD_MCP_HTTP_TOKEN
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.12) reached the registry yesterday.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Context7, Codebase Memory, Exa
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Codebase Memory
by DeusData
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Runs on your computer★ 48,148MITUpdated 20 days ago
Install
Exa
by exa-labs
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Runs in the cloud★ 5,213MITUpdated last month
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Zammad + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP
Unofficial. Community-built Claude Code Skill and MCP server for the Zammad
API. Not affiliated with, endorsed by, or sponsored by Zammad GmbH.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every Zammad ticket, article, and Knowledge Base operation as one CLI and MCP server - plus a team-management layer (agent load, customer health, aging backlog, escalation triage, churn risk, feedback mining) the Zammad API can't answer in a single call. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.
Works with your agent
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Zammad skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register zammad-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add zammad-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add zammad-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs zammad-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote server, which msp-skills does not support yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list. Setup steps: mcp-install.md.
Also for the Microsoft and Google stacks
Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).
Run more than one agent? Install across all 51+ supported agents in one command:
npx skills add Servosity/msp-skills@latest(requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.
Install in 60 seconds
Fastest for Claude Desktop - one-click .mcpb
Claude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companionzammad-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or setZAMMAD_CLI_PATHto an existing binary). Details: #331.
Download Zammad MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Zammad release on the releases page.)
Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:
/plugin marketplace add Servosity/msp-skills/plugin install zammad@msp-skills
Path A - paste one prompt into your AI agent (recommended)
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Zammad Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zammad/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zammad/install.ps1 | iex. Then authenticate per the README and runzammad-cli --helpto explore.
The same prompt works in any agent that can run shell.
Path B - run the installer yourself
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zammad/install.ps1 | iexmacOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zammad/install.sh)The installer drops both zammad-cli (the CLI) and zammad-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
zammad-cli --versionUpgrade to the latest version
The installer always fetches the current release - re-run it to upgrade:
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zammad/install.sh)Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zammad/install.ps1 | iexClaude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update zammad@msp-skills.
Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client
After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.
Install for Hermes
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/zammad --forceInside a Hermes chat session:
/skills install servosity/msp-skills/skills/zammad --forceHermes speaks MCP natively, so it can also use the zammad-mcp server directly - same install path, same env vars.
Install for OpenClaw
Tell your OpenClaw agent (copy this):
Install the zammad skill from https://github.com/servosity/msp-skills/tree/main/skills/zammad. The skill defines how its required CLI (
zammad-cli) can be installed via theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Authenticate
Set the credentials the CLI needs (from your Zammad portal):
ZAMMAD_API_TOKEN=<value> zammad-cli doctordoctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.
What this skill does
| Question your team keeps asking | Command |
|---|---|
| Who on support is overloaded right now? | zammad-cli agent-load --json |
| Is each agent's queue growing or shrinking? | zammad-cli agent-trend --weeks 4 --json |
| Which customers are struggling and need attention first? | zammad-cli customer-health --at-risk --json |
| What tickets have been open too long? | zammad-cli overdue --days 3 --json |
| Which customers sound upset and should be escalated? | zammad-cli escalate --json |
| Which accounts are trending toward churn, and why? | zammad-cli churn-risk --json |
| What are customers asking for (features, pricing, compliance)? | zammad-cli feedback-scan --bucket pricing --json |
| Find and read open tickets (scope to a customer with organization_id:N) | zammad-cli tickets search --query "state:open" --json |
| Log a note or search the Knowledge Base | zammad-cli ticket note 12345 --body "..." --internal · zammad-cli kb search "restore" --json |
| Hear about new and changed tickets as they happen, without polling | zammad-cli webhooks listen · zammad-cli events list --since 0 --json |
New tickets as they happen (webhooks)
Zammad can call this machine when a ticket is created or updated or an article is added, so nothing has to poll it.
# Once, with a token that has the admin.webhook and admin.trigger permissionszammad-cli webhooks register --endpoint http://127.0.0.1:8789/zammad --yes
Keep running on the machine Zammad posts to
zammad-cli webhooks listen
Read what arrived; pass the returned cursor as --since next time
zammad-cli events list --since 0 --json
registercreates one Zammad webhook and one trigger per event (zammad.ticket.created,zammad.ticket.updated,zammad.article.created). It generates the signature secret and stores it beside your API token, readable only by you;ZAMMAD_WEBHOOK_SECREToverrides it. The secret is never printed:webhooks statusshows only where it comes from.listenbinds to this machine only (127.0.0.1, port 8789) by default and refuses to start without the secret. Every request must carry Zammad'sX-Hub-Signature, checked before the body is read; a delivery it has already seen is dropped, and bodies over 1 MiB are refused.- The webhook carries IDs only. The listener fetches the ticket through the API and records the event, so customer text never travels in the webhook.
- Zammad gives up on a delivery after five attempts over about two minutes. Each time
listenstarts, it first records what changed while it was down. A delivery Zammad gives up on whilelistenis running but cannot be reached (a network outage) is not recorded. - Zammad has to reach the listener. A self-hosted Zammad on the same server works with the default. Zammad on another machine on your LAN needs
listen --addr :8789 --tls-cert --tls-keyand anhttps://endpoint. A Zammad Cloud instance cannot reach a machine on your LAN. - Over MCP,
events_listreads the recorded events (read-only, no Zammad call).webhooks_registerandwebhooks_unregisterchange Zammad only withconfirm: true.listenis CLI-only.
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
What makes this different
Most Zammad integrations and MCP servers proxy each question into a live API ca
Only the beginning is shown; read the rest in the repo