Skip to main content
Glama

Related Servers

Alternatives to kustomer-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to inspect and manage customer-service consultations through MCP tools, including reading conversations and, after explicit confirmation, replying, assigning managers, and updating status. Write actions are disabled and contact details masked by default.
      144 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP-compatible agents to perform read-only incident investigations by querying logs, building timelines, searching runbooks, validating evidence, and creating ticket drafts only with explicit approval.
      7
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to audit and analyze Zendesk instances through a read-only MCP interface, providing tools for triggers, automations, analytics, and cross-reference queries.
      74
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants read-only access to Sprinklr data via MCP, allowing querying reports, searching cases, and calling Sprinklr API endpoints.
      8 npm
      ISC
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only inspection of Google Ads accounts through MCP, including account inventory, reporting, metadata, change history, and safe GAQL queries.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP-capable AI clients to read a local AI ticket triage queue and human decision log through four read-only tools for checking queue status, listing pending review items, viewing recent decisions, and searching decisions. It does not allow approving, rejecting, or sending anything.
      4
      MIT

    TDQS

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct resource: conversations (list vs. single-thread read), knowledge base search, bot tool-call logs, and billing usage. The list/get conversation pair is clearly delineated in the descriptions (preview vs. full thread), and no two tools could be reasonably confused.

    Naming Consistency5/5

    All five tools follow a strict verb_noun snake_case pattern: get_conversation, list_conversations, search_knowledge, get_tool_calls, get_usage. The verb choice also matches the operation semantics (list for collections, get for single resources).

    Tool Count5/5

    Five tools is a tight, well-scoped surface for a read-only observability/debugging server; every tool maps to a distinct investigative question (what was said, what was retrieved, what tools fired, what it cost). Nothing feels padded or missing at the count level.

    Completeness4/5

    The surface covers the core diagnostic loop: find a conversation, read it, verify what knowledge was used, inspect bot tool calls, and check usage. Gaps are minor for a read-only server—no ability to reply, change handover status, or filter conversations by customer/date—but agents can work around these by escalating elsewhere.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues