Skip to main content
Glama
xalantis-hub

Xalantis MCP Server

Official
by xalantis-hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Xalantis MCP Server

No user-submitted related servers found.

    Related Servers

    • osTicket MCP Server

      tecnologicachile
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI-driven management of osTicket helpdesks through natural language, allowing users to reply to, assign, and transfer tickets without requiring API keys. It reverse-engineers the osTicket staff panel to provide full access to ticket operations using session-based authentication.
      2
      -

    • Helpdesk Mender MCP

      headlessherm-creator
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create tickets, post public replies, add private internal notes, change ticket status, and list tickets across Zendesk, Freshdesk, and Help Scout using one consistent tool vocabulary and unified credential setup. It handles each platform's differing authentication schemes and field conventions, including Help Scout's non-refreshable OAuth2 client-credentials tokens.
      388 npm
      MIT

    • NKS osTicket MCP

      nks-hub
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to manage osTicket support tickets including listing, searching, reading, creating, updating, replying, deleting, managing subtickets, and downloading attachments.
      14
      3
      MIT

    • gorgias-mcp

      NoBanks
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage Gorgias support tickets: list open tickets, read conversation history, draft internal notes, send outbound replies (gated), and look up customer history.
      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

    A3.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: creating, retrieving, listing, replying to, updating tickets, and listing replies. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_ticket, list_tickets, reply_to_ticket), making them predictable and easy to understand.

    Tool Count5/5

    Six tools is an appropriate number for a focused ticketing system. Each tool addresses a core operation without unnecessary redundancy or bloat.

    Completeness4/5

    The tool set covers the main lifecycle of a ticket: create, read, update, list, and add replies. A delete ticket or advanced search tool is missing, but these are minor gaps for a basic implementation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources