Skip to main content
Glama
bitterdev

simple-support-system-mcp

by bitterdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to simple-support-system-mcp

No user-submitted related servers found.

    Related Servers

    • ticksy-mcp

      artkrsk
      A
      license
      A
      quality
      D
      maintenance
      MCP server for the Ticksy support ticket API, enabling AI agents to read and write support tickets.
      16
      3 npm
      MIT

    • swsd-mcp

      mikimatsub
      A
      license
      A
      quality
      A
      maintenance
      MCP server for SolarWinds Service Desk (SWSD/Samanage) enabling reading and modifying tickets, comments, knowledge-base articles, and more via each user's own API token.
      37
      280 npm
      4
      MIT

    • drupalorg-mcp

      zaporylie
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for drupal.org's public REST API. Enables querying projects, issues, comments, and user information on drupal.org.
      7 npm
      GPL 2.0

    • kanban-mcp

      Rafael09ED
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for task/ticket management with dependency tracking, supporting CRUD operations, status management, project filtering, and automatic data migrations.
      8 npm
      1
      -
    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

    A4/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action across tickets, comments, projects, and attachments, and descriptions clarify the boundaries (e.g., reply_to_ticket creates a comment while update_comment edits it, upload_attachment vs add_ticket_attachments vs delete_attachment are cleanly separated). An agent can reliably pick the right tool without guessing.

    Naming Consistency5/5

    Consistent snake_case verb-first naming throughout: list_/get_/create_/update_/delete_ for resources, plus clear action verbs like set_ticket_state, reply_to_ticket, approve_ticket. The only deviations (list_ticket_comments, add_ticket_attachments) follow the same pattern.

    Tool Count4/5

    23 tools is on the heavier side, but the surface spans four resources (tickets, comments, projects, attachments) each needing full lifecycle plus moderation and state handling, so nearly every tool earns its place. Slightly over the comfortable range but justified by scope.

    Completeness4/5

    Strong coverage: full CRUD for tickets and projects, comment management with moderation, attachment upload/link/download/delete lifecycle, and state transitions. Minor gaps remain, such as no way to list users to resolve assigneeUserId and no standalone create_comment (covered by reply_to_ticket).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources