Skip to main content
Glama
chrischall

accessoticketing-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to accessoticketing-mcp

No user-submitted related servers found.

    Related Servers

    • mysql-mcp

      zuozhu20100425
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables secure, read-only access to MySQL databases with structured query tools, and optional opt-in write operations when explicitly enabled.
      1,011 npm
      MIT

    • hit-mcp

      DevpeakAB
      A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for the HIT ticket management system that lists queues, searches/fetches ticket details, and lists ticket templates.
      4
      10 npm
      1
      MIT

    • Edenred Plus MCP

      B-Mahdj
      A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for Edenred Plus that enables checking benefit balances, transactions, and deals via local browser authentication.
      5
      MIT

    • abm-mcp

      o-sokhan
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that provides tools to list and read devices, MDM servers, blueprints, configurations, apps, packages, users, and other resources from Apple Business Manager and Apple School Manager.
      MIT

    • tokenless-zendesk-mcp

      yutamago
      A
      license
      A
      quality
      C
      maintenance
      MCP server that authenticates via browser session cookies to access Zendesk's REST API without API tokens, supporting reads and writes with agent permissions.
      19
      21 npm
      1
      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

    A4.1/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct purpose: order-level reading (get_order), single-admission drill-down (get_ticket), barcode export (save_barcodes), wallet links (get_wallet_passes), link unwrapping (resolve_link), and connectivity (healthcheck). The only mild overlap is between get_order and get_ticket, since get_order already returns per-admission details, but the index-based 'full detail plus terms' framing differentiates them adequately.

    Naming Consistency4/5

    All names use a consistent accesso_ prefix with snake_case verb_noun or noun forms (get_order, get_ticket, save_barcodes, resolve_link), which is highly predictable. healthcheck is the sole outlier, lacking an explicit verb, but it remains readable and consistent in casing.

    Tool Count5/5

    Six tools is a well-scoped set for a read-oriented accesso ticket client, with each tool earning its place (order read, ticket detail, barcodes, wallet, link resolution, healthcheck). No redundancy or padding.

    Completeness4/5

    The surface covers the full read lifecycle from link resolution through order/ticket detail, barcodes, and wallet passes, with no obvious dead ends. Write operations are legitimately out of scope, though there is no way to enumerate or search multiple orders, which is a minor gap.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources