Skip to main content
Glama
JhinxDev

Scoped Support MCP

by JhinxDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Scoped Support MCP

No user-submitted related servers found.

    Related Servers

    • helpdesk

      karnstack
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants and signed-in support staff to search and read customer tickets, add internal notes, issue refunds under per-scope and per-customer limits, and export ticket data over a remote, OAuth-protected Streamable HTTP endpoint. Tool lists, resources, prompts, and write operations are gated by bearer tokens and audience-bound scopes so that refund and export actions stay bounded.
      6
      1
      MIT

    • Zendesk MCP Server

      clambert2617
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables operators to retrieve and manage support tickets, comments, and attachments, and to draft or analyze ticket responses using help center articles as a knowledge base. Access uses per-operator OAuth so each person's own permissions and identity apply to every action.
      -

    • Freshdesk Agent Studio

      Shaambhavi58
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely list, retrieve, and search Freshdesk support tickets through typed read-only MCP tools. It supports API-key authentication, rate-limit handling, safe logging, and an offline fictional demo mode.
      -

    • OpsPilot MCP Server

      fferjani94
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only, deterministic tools for searching accounts and knowledge and retrieving tickets, ticket details, and product information over a stdio MCP connection.
      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.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    list_tickets and get_ticket have clearly distinct purposes: enumerate a bounded collection versus retrieve a single record by identity. There is no overlap or plausible misselection between the two.

    Naming Consistency5/5

    Both tools follow a clean verb_noun pattern (list_tickets, get_ticket) using consistent snake_case. The convention is predictable and would extend naturally to future tools.

    Tool Count3/5

    Only 2 tools for a support/ticket domain is thin, even for an explicitly scoped demo identity server. The set covers retrieval but nothing beyond it, so it sits at the borderline of under-scoped.

    Completeness2/5

    The surface is read-only: tickets can be listed and fetched but never created, updated, commented on, or closed. For a support ticket domain this leaves significant lifecycle gaps that would block most agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources