Deskpro MCP by usefulapi

Most tools target a distinct resource and action, but there is some overlap: deskpro_list_people includes agents while deskpro_list_agents is agent-specific, and deskpro_list_tickets overlaps with the person/organization ticket listing tools and search. Descriptions clarify these boundaries, so misselection is possible but not likely for an attentive agent.

All tools use a consistent deskpro_ prefix followed by snake_case verb_noun names (create_ticket, get_ticket, list_tickets, update_ticket). The only minor variation is deskpro_search, which omits an explicit noun but still fits the verb-first convention.

With 20 tools, the set is borderline heavy for an MCP server. Several list endpoints are convenient rather than essential because broader tools like list_tickets already support filtering by person or organization.

Core ticket workflows are covered well: create, get, update, list, messages, and status lookup. However, there are notable gaps in write operations for other entities: no update/delete for people, organizations, or tickets, and knowledgebase articles are read-only.