Skip to main content
Glama
ProtosaurusRex

custsupport

by ProtosaurusRex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to custsupport

No user-submitted related servers found.

    Related Servers

    • Tickets and Warehouse MCP

      ManyuRV
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes a synthetic issue tracker and pipeline warehouse as callable tools so an agent can answer operational questions about tickets, pipeline health, runs, incidents, and governed metrics with every claim cited to the exact tool call it came from. All writes are proposal-only, requiring human approval through a gated apply path that logs each step for audit.
      MIT

    • customer-support-mcp

      wtf-amnn
      F
      license
      A
      quality
      C
      maintenance
      Enables Claude to manage customers and support tickets through database-backed CRUD tools, contextual customer and knowledge resources, and a reusable ticket-triage prompt.
      13
      -

    • TiendaTech Support MCP Server

      nudge-digital-lab
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes read-only knowledge base articles on returns, warranty and shipping policies alongside tools that search, retrieve and create real support tickets. This lets an LLM agent ground its answers in store policy without inventing information, and act on actual ticket data rather than simulated records.
      -

    • Customer Support Analyst MCP

      ZivSapir
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language Q&A over customer support ticket data. Provides tools for schema inspection, SQL-based ticket counts and grouping, and full-text search for customer wording without requiring API keys.
      -

    • zendesk-mcp

      sophiabanda
      A
      license
      A
      quality
      B
      maintenance
      Enables Zendesk support workflows through tools for semantic ticket search, customer context retrieval, solution version assessment, and daily work summaries.
      4
      28 npm
      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.2/5.0

    Scored across 9 tools

    Disambiguation4/5

    Tools are largely distinct, but aggregation tools like daily_digest, category_breakdown, and sla_risk_summary overlap in the data they summarize, which could lead to misselection. Descriptions clarify their differences, but the boundary between daily_digest and category_breakdown is subtle.

    Naming Consistency4/5

    Names follow snake_case and are generally clear, but mix verb-first (list_open_tickets, get_ticket) with noun-first patterns (sla_breaches, category_breakdown). Despite the mix, the naming is predictable and readable, with no camelCase or chaotic variations.

    Tool Count5/5

    9 tools is well within the ideal 3-15 range for a focused domain. Each tool covers a distinct part of the support workflow—listing, detail, aggregation, SLA monitoring, draft replies, escalation, and status updates—without redundancy or bloat.

    Completeness4/5

    The surface covers the main support lifecycle: read (list, get), aggregate (breakdowns, SLA risk), assist (draft reply, escalation), and write (update status). Minor gaps exist, such as no tool to create or assign tickets, but these may be handled externally. The core workflow is well supported with no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources