Skip to main content
Glama
aminafara123

triage-mcp

by aminafara123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to triage-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • openstack-incidents

      jiang369-lucky
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP-compatible agents to perform read-only incident investigations by querying logs, building timelines, searching runbooks, validating evidence, and creating ticket drafts only with explicit approval.
      7
      MIT

    • Zendesk MCP Server

      rlowndes9
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to audit and analyze Zendesk instances through a read-only MCP interface, providing tools for triggers, automations, analytics, and cross-reference queries.
      74
      MIT

    • Enterprise Knowledge

      AjaneeI
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables users to check whether procedures are current and whether actions have the stored evidence needed for human review, returning status, citations, and blockers through read-only MCP tools while always requiring human review.
      -
    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.5/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct primary purpose: queue_status gives counts, pending_items lists reviewable tickets, recent_decisions browses the audit log, and search_decisions queries that same log. There is mild overlap between queue_status/pending_items and between recent_decisions/search_decisions, but the descriptions clearly separate them.

    Naming Consistency4/5

    All names use consistent snake_case and follow a two-part modifier+noun pattern (queue_status, pending_items, recent_decisions, search_decisions). The only minor deviation is search_decisions using a verb_noun form while the others are noun/noun or adjective/noun.

    Tool Count5/5

    Four tools is well-scoped for a read-oriented triage inspection/audit server. Each tool covers a distinct facet (status counts, pending list, recent decisions, decision search) without redundancy.

    Completeness3/5

    The surface covers read/inspection operations well, but there is no tool to submit a decision (approve, edit, reject) or otherwise act on a ticket. For a triage workflow, that is a notable missing write operation that limits the set to monitoring only.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources