zammad-mcp
Related Servers
Alternatives to zammad-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server to interact with Zammad ticketing system, enabling ticket search, creation, update, article addition, and user/organization/group queries via the Zammad API.-
- AlicenseNot gradedqualityBmaintenanceA remote MCP server for Zammad, enabling ticket management, search, and OAuth authentication.27 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that connects AI assistants to Zammad, providing tools for managing tickets, users, organizations, and attachments.49AGPL 3.0
- AlicenseAqualityBmaintenanceEnables MCP clients to interact with Zammad tickets, articles, search and replies under each caller's own permissions, using either a static token or SSO/OIDC per-user mode.1MIT
- AlicenseAqualityBmaintenanceModel Context Protocol (MCP) server for German Electronic Invoicing (ZUGFeRD 2.x / XRechnung 3.x). Provides tools to validate, generate, parse, and convert invoices compliant with EN 16931 and KoSIT.50112 PyPI2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA self-hosted MCP server that lets each agent connect their own Freshdesk tenant with a personal API key via OAuth, then read tickets, contacts, companies, agents, groups and knowledge, and perform writes through expiring previews with interactive confirmation and readback verification. It optionally indexes local history to provide semantic search with fresh access checks before returning evidence.MIT
TDQS
Scored across 3 tools
The three tools target clearly distinct actions: reading a ticket thread, writing a customer-facing draft, and adding an agent-only internal note. Descriptions explicitly cross-reference each other (the note tool points to the draft tool for customer replies), eliminating misselection risk.
All tools use a uniform zammad_<verb>_<noun> snake_case pattern (zammad_create_shared_draft, zammad_add_internal_note, zammad_get_ticket_thread) with distinct, accurate verbs. No mixed conventions.
Three tools is thin even for a deliberately narrow drafting assistant; there is no tool for locating tickets (search/list) or fetching ticket metadata without articles. The count is defensible given the tightly scoped purpose but feels borderline.
Core lifecycle (read thread → draft reply / add note) is covered, and the omission of a send tool is intentional with a documented human-in-the-loop path. However, there is no way to discover or search tickets, so an agent must already know the ticket ID, and there is no way to inspect or discard an existing draft.