Skip to main content
Glama
webmilmind1

DeskCrew MCP Server

by webmilmind1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to DeskCrew MCP Server

No user-submitted related servers found.

    Related Servers

    • TicketDesk MCP

      bhargavlukka
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search and retrieve support tickets, add notes, close tickets, and access SLA policies through MCP tools, resources, and prompts over Streamable HTTP.
      MIT

    • Ticket Queue MCP Server

      sanjay1110
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to access and manage an internal support ticket queue through MCP tools, resources, and prompts, including searching and viewing tickets, adding comments, closing tickets with confirmation, reading knowledge base articles, and viewing queue summaries over OAuth-secured Streamable HTTP.
      -

    • SecureMCP Agent Hub

      sgt-9304
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely call enterprise MCP tools with tenant-scoped RBAC, human approvals, audit logging, and multi-tool workflows across customer, order, document, and ticket data.
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 23 tools

    Disambiguation3/5

    Most tools are clearly scoped, but draft_reply and propose_resolution overlap heavily: both create a draft response awaiting human approval for a tickethol_0. Similarly, resolve and close might be ambiguous if present, but here the overlap is mainly between the two draft-submitting tools. search_tickets vs list_tickets are distinguished implicitly (search vs list) but could still cause hesitation.

    Naming Consistency4/5

    The verb_noun pattern is mostly consistent (list_tickets, search_tickets, draft_reply, create_issue), with a few clear descriptive names like get_ticket_context, rotate_board_key, and preflight_bounty that don't follow the pattern but are still readable and unambiguous.

    Tool Count4/5

    23 tools is on the high side but each maps to a distinct operation and the domain (ticketing, knowledge base, issues, bounties, board keys) is broad enough to justify it. A handful are near-duplicates (draft_reply vs propose_resolution vs draft_support_reply) which leans toward the upper bound.

    Completeness4/5

    The lifecycle is well covered: search/list → get_context → draft → send → resolve, with issue linking and changelog/roadmap lookup. Minor gaps: no tool to update a ticket's status directly (only via draft/resolve), no KB write/update tooling, and no way to list or revoke drafts.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources