Scoped Support MCP
Related Servers
Alternatives to Scoped Support MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Zendesk ticket data for customer support analysis and insights. It supports searching tickets by tags or keywords, retrieving ticket details, and analyzing agent performance and service trends.-
- FlicenseNot gradedqualityCmaintenanceExposes 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.-
- FlicenseNot gradedqualityCmaintenanceExposes three customer-support tools over JSON-RPC: looking up order status (with sensitive customer fields withheld), keyword-searching store policy sections, and creating idempotent support tickets tied to existing orders. Each tool's arguments are validated and published as JSON Schema, so any MCP client can discover and safely invoke them.-
- FlicenseAqualityBmaintenanceProvides MSP support tools (ticket search, draft response, KB search, update) with a deterministic security guardrail that refuses to draft responses for security tickets based on content scanning, even if mislabeled.5-
- AlicenseNot gradedqualityBmaintenanceEnables ticket and contact management via Freshdesk API v2, including listing, searching, and retrieving support tickets and customer contacts.128 npmMIT
TDQS
Scored across 2 tools
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.
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.
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.
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.