F
licenseNot graded
qualityA
maintenanceEnables retrieving and managing tickets and comments, analyzing tickets, drafting responses, and accessing Help Center articles as a knowledge base.
-
internal-ops
by minaelzek
Related Servers
Alternatives to internal-ops
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables users to retrieve and manage tickets and comments, analyze tickets and draft responses, and access Help Center articles as a knowledge base.-
- FlicenseNot gradedqualityAmaintenanceEnables users to retrieve and manage support tickets and comments, analyze tickets, draft responses, and access help center articles through a Model Context Protocol integration with OAuth-backed per-user permissions.-
- FlicenseNot gradedqualityAmaintenanceEnables 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.-
- FlicenseNot gradedqualityAmaintenanceEnables retrieving and managing support tickets and comments, analyzing tickets and drafting responses, and searching Help Center articles as a knowledge base. Authenticates each operator through OAuth so API calls carry their own Zendesk identity and permissions.-
- FlicenseNot gradedqualityAmaintenanceEnables users to retrieve and manage tickets and comments, analyze tickets, draft responses, and access Help Center articles as a knowledge base, with OAuth-based per-operator permissions.-
TDQS
A3.5/5.0
Scored across 5 tools
Disambiguation5/5
The tool set splits cleanly into two resource families (docs and tickets), and within each family the actions are distinct: search_docs searches while get_doc fetches a single article, and list_open_tickets lists while get_ticket and create_ticket operate on a single ticket. No two tools could reasonably be confused for one another.
Naming Consistency5/5
All five tools follow a strict snake_case verb_noun pattern (search_docs, get_doc, list_open_tickets, get_ticket, create_ticket), with verbs that accurately signal the operation. The only variance is the natural doc/docs singular-plural distinction, which is idiomatic rather than inconsistent.
Tool Count4/5
Five tools is on the lean side but every tool serves a distinct purpose and none is redundant. It is slightly thin for an 'internal-ops' surface that touches both documentation and ticketing, but well within a reasonable scope.
Completeness3/5
The ticket lifecycle is a dead end: tickets can be created and read, but there is no update, close, resolve, or comment/note operation, so an agent cannot act on the tickets it lists. The docs side is read-only, which is plausible for a help center but leaves no way to enumerate articles beyond keyword search.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues