Skip to main content
Glama
glira

mcp-tomticket

by glira
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-tomticket

No user-submitted related servers found.

    Related Servers

    • SparrowDesk by sparrowdesk

      SparrowDeskofficial

      sparrowdesk
      F
      license
      Not graded
      quality
      B
      maintenance
      Connect to SparrowDesk using MCP and manage your tickets, knowledge base and more.
      1
      -

    • zammad-mcp

      marcelofmatos
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server to interact with Zammad ticketing system, enabling ticket search, creation, update, article addition, and user/organization/group queries via the Zammad API.
      15 npm
      MIT

    • relation-mcp

      sewon-supernova
      A
      license
      B
      quality
      C
      maintenance
      Enables to interact with Re:lation support tickets via MCP. Allows searching, updating, replying to tickets, and managing customers and internal records.
      11
      8 npm
      MIT

    • ticksy-mcp

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

    • i-net HelpDesk MCP Server

      roddyst
      A
      license
      A
      quality
      B
      maintenance
      MCP server that exposes the i-net HelpDesk Ticket Web-API as tools for AI agents, enabling ticket search, reading, creation, and actions like replying, closing, and escalating, with attachment support.
      8
      MIT
    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

    B3.1/5.0

    Scored across 49 tools

    Disambiguation3/5

    Most tools are clearly distinct, but several families overlap: tomticket_list_departments already includes categories, operators, and statuses, while separate department-list tools exist. Similarly, tomticket_list_custom_fields overlaps with five scoped custom-field listers. The descriptions help, but the boundaries are not always obvious in a 49-tool set.

    Naming Consistency4/5

    The tools overwhelmingly follow a clear tomticket_verb_noun snake_case pattern, such as list_tickets, create_customer, and finish_ticket. Minor deviations like tomticket_customer_exists and tomticket_customer_quick_access break the verb-first convention, but the overall naming scheme remains predictable and readable.

    Tool Count2/5

    49 tools is well above the 25+ threshold and creates unnecessary navigation burden. Many tools could be consolidated with parameters, such as the six custom-field listers and four department listers, making the surface heavier than the domain requires.

    Completeness3/5

    Core ticket, customer, and article workflows are well covered, including mutation operations. However, notable gaps exist: there is no general ticket update/delete, no delete for articles/customers/organizations, no article-category management beyond listing, and chat tools are read-only with no reply capability.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources