Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"zammad-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Zammad MCP Server An MCP server exposing a Zammad helpdesk to a model. Built on [`zammad-python-client`](https://gitlab.codefighters.de/python/zammad-python-client); it owns tool design, safety and response shaping and no HTTP logic at all. Fifteen tools shaped like support jobs, not CRUD: | Tool | Does | Writes | | :-- | :-- | :-- | | `find_customer` | People and organizations by name, email, login | no | | `search_tickets` | Zammad query syntax or free text; summaries only | no | | `get_ticket` | One ticket with conversation (as text), tags, booked time | no | | `reference_data` | Groups, states, priorities, time types with ids | no | | `create_ticket` | New ticket for a customer with an internal opening note | yes | | `add_note` | Internal note, optional time booking | yes | | `reply_to_customer` | Stores a **draft** note by default; mails only with `send=true` | yes | | `update_ticket` | State, priority, owner, group, title, pending time, with a note | yes | | `log_time` | Book time on a ticket | yes | | `search_knowledge` | Knowledge base search as agent (internal + public) | no | | `get_answer` | One answer, body as text | no | | `write_answer` | New answer, set to **internal** (agents only) | yes | | `update_answer` | Change title/body of one translation, or move the answer; visibility untouched | yes | | `create_category` | New knowledge-base category, optionally nested | yes | | `kb_structure` | Knowledge bases, locales, categories with ids | no | Deliberately absent: delete anything, merge tickets, publish an answer publicly, mail a customer without `send=true`. Every write is something an agent does all day and can undo in the UI. ## Install On PyPI as `zammad-mcp`; the server itself needs no install step: ```bash claude mcp add --scope user zammad -e ZAMMAD_URL=https://zammad.example.com -e ZAMMAD_TOKEN=... -- uvx zammad-mcp ``` Any MCP client: command `uvx`, args `["zammad-mcp"]`, env `ZAMMAD_URL` and `ZAMMAD_TOKEN`. Teams on our marketplace …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.