Skip to main content
Glama
eduardoantoniojunior

OTRS MCP Server

by eduardoantoniojunior
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to OTRS MCP Server

No user-submitted related servers found.

    Related Servers

    • soporte-ti-mcp

      raulperez0798
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides IT support tools to search known incidents, check ticket status, and create ticket drafts, enabling an AI assistant to help users with IT support queries.
      -

    • freshservice-mcp

      mchluba
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with Freshservice service desk, supporting ticket search, retrieval, and creation via a configurable, Docker-first deployment.
      MIT

    • Personal JIRA MCP

      yuezheng2006
      A
      license
      C
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with JIRA, allowing for querying issue details, creating and updating work items, and managing attachments through a standardized interface.
      12
      4
      MIT
    • tickiti-mcp by tickiti

      tickiti-mcpofficial

      tickiti
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that exposes the Tickiti helpdesk API to AI assistants, enabling ticket management and helpdesk operations via natural language.
      11
      MIT

    • Zammad MCP Server

      basher83
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that connects AI assistants to Zammad, providing tools for managing tickets, users, organizations, and attachments.
      42
      AGPL 3.0
    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

    B3.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation on tickets: create, retrieve individual details, search, update, and retrieve history. There is no meaningful overlap between get_ticket and get_ticket_history because one returns current state and the other returns the audit trail.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case: create_ticket, get_ticket, search_tickets, update_ticket, get_ticket_history. The only minor variation is the plural 'tickets' in search_tickets, which is natural and does not break the pattern.

    Tool Count5/5

    Five tools is well-scoped for a ticket management server. Each tool represents a core operation without unnecessary redundancy, making the set easy to navigate.

    Completeness5/5

    The tool surface covers the essential ticket lifecycle: creation, retrieval, search, update, and history lookup. For OTRS, this is a complete and practical set with no obvious dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources