Skip to main content
Glama
karnstack

helpdesk

by karnstack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to helpdesk

No user-submitted related servers found.

    Related Servers

    • Ticket Queue MCP Server

      sanjay1110
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to access and manage an internal support ticket queue through MCP tools, resources, and prompts, including searching and viewing tickets, adding comments, closing tickets with confirmation, reading knowledge base articles, and viewing queue summaries over OAuth-secured Streamable HTTP.
      -

    • TicketDesk MCP

      bhargavlukka
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search and retrieve support tickets, add notes, close tickets, and access SLA policies through MCP tools, resources, and prompts over Streamable HTTP.
      MIT

    • Zendesk MCP Server

      JosephBrooks6039
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to retrieve and manage tickets and comments, and to search Help Center articles as a knowledge base from an AI client. Includes prompts for analyzing tickets and drafting responses, with per-operator OAuth authentication so each person's own Zendesk permissions apply.
      -

    • ops-mcp

      Fuzailkazi
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables SaaS support desk operations with sixteen tools for customer lookup, invoice and ticket access, refunds, and admin actions, organized into four risk tiers.
      -
    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.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: search vs. get for tickets, get for customers, export, note addition, and refund. Boundaries are clear, and the ticket lookup pair is well differentiated (bulk search vs. single-ticket detail).

    Naming Consistency5/5

    All names follow a consistent verb_noun snake_case pattern (search_tickets, get_ticket, get_customer, export_tickets, add_internal_note, issue_refund). No mixed conventions or vague verbs.

    Tool Count5/5

    Six tools is well-scoped for a helpdesk surface, with each tool clearly earning its place. No redundancy or thin coverage.

    Completeness3/5

    Read and write operations cover lookup, export, notes, and refunds, but there is no ticket creation, status update/close, or customer-facing reply, which are core helpdesk lifecycle actions. These gaps will limit end-to-end agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources