Skip to main content
Glama
BM1-de

zammad-mcp

by BM1-de
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to zammad-mcp

No user-submitted related servers found.

    Related Servers

    • zammad-mcp

      marcelofmatos
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server to interact with Zammad ticketing system, enabling ticket search, creation, update, article addition, and user/organization/group queries via the Zammad API.
      3 npm
      MIT

    • Zammad MCP Server

      basher83
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that connects AI assistants to Zammad, providing tools for managing tickets, users, organizations, and attachments.
      41
      AGPL 3.0

    • mcp-einvoicing-de

      cmendezs
      A
      license
      A
      quality
      A
      maintenance
      Model 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.
      50
      218 PyPI
      2
      Apache 2.0

    • mcp-mail

      PilarJ
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing read and send access to a single IMAP/SMTP mailbox over Streamable HTTP with GitHub OAuth authentication, featuring recipient allowlists for security, email reading/searching/threading, attachments, drafts, folder management, and sending/reply tools.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one adds an internal note, the other fetches a ticket with all articles. No overlap or confusion possible.

    Naming Consistency5/5

    Both tools follow the consistent pattern 'zammad_verb_noun' (add_internal_note, get_ticket_thread), making naming predictable.

    Tool Count2/5

    Only 2 tools for a Zammad ticketing system, which typically requires many more operations (create, list, update tickets, etc.). The set feels insufficient for the domain's scope.

    Completeness1/5

    Severely incomplete: basic CRUD operations like create, list, or update tickets are missing. The tool description references 'zammad_create_shared_draft' but it's not available, leaving agents unable to perform customer-facing actions.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources