Skip to main content
Glama
odelvalle

MCP Customer Support Example

by odelvalle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to MCP Customer Support Example

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • SecureAgentServer

      bhargavlukka
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables secure support-ticket and customer-account operations with signed JWT authentication, prompt-injection and tool-poisoning guardrails, and human-in-the-loop confirmation for destructive actions.
      MIT

    • Bumblewick Support-Desk MCP

      Saveanu-Robert
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage customer support for a fictional candle shop, including order lookup, customer file access, and safe refund processing with server-side safety rules.
      MIT

    • return-billing-mcp-server

      GT5041
      F
      license
      A
      quality
      B
      maintenance
      MCP server that provides tools for order lookup, return eligibility checks, return processing, billing status, and human escalation, simulating a return/billing inquiry triage system using local JSON data.
      5
      -

    • tessera-mcp

      NDilanka
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to manage a fictional B2B workspace SaaS (Tessera) with tools for ticketing, invoicing, customer management, and trial extensions, featuring a human-in-the-loop confirm pattern for safety.
      7
      6 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 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: calculating refund eligibility, creating tickets, listing orders, getting profiles, requesting refund approval, and sending emails. There is no functional overlap between any two tools.

    Naming Consistency5/5

    All tool names follow a consistent verb+noun pattern in camelCase (e.g., calculateRefundEligibility, createSupportTicket), with no deviations or mixed conventions.

    Tool Count5/5

    With 6 tools covering customer order lookup, profile access, refund eligibility, ticket creation, refund approval requests, and email notifications, the count is well-scoped for a customer support demo or small-scale integration.

    Completeness4/5

    The tool set covers the core customer support workflow—viewing orders and profiles, creating tickets, checking and requesting refunds, and sending emails. Minor gaps include lack of ticket update or order cancellation, but the essential interactions are present.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources