Skip to main content
Glama
dragosh29

TicketSource MCP server

by dragosh29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to TicketSource MCP server

No user-submitted related servers found.

    Related Servers

    • ops-agent-mcp

      ramonpalopoli
      A
      license
      A
      quality
      C
      maintenance
      Enables any MCP client to run natural-language queries and actions against CRM and ticket systems, with schema-validated tools, audit logging, and server-side write gating.
      7
      MIT

    • TryBooking MCP Server

      marek-knappe
      F
      license
      B
      quality
      B
      maintenance
      An MCP server that wraps the TryBooking Reporting API, enabling AI assistants like Claude to query bookings, events, sales reports, and attendance scans.
      15
      -

    • libredesk-mcp

      metanmai
      A
      license
      C
      quality
      D
      maintenance
      MCP server that exposes the complete Libredesk REST API (54 endpoints) as tools, enabling natural language management of conversations, contacts, agents, teams, and more for the open-source customer support desk.
      54
      3 npm
      4
      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/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: events, performances, bookings, and customers are clearly separated. Even list_events and list_upcoming_performances differ in scope (all events vs. upcoming performance dates), eliminating ambiguity.

    Naming Consistency5/5

    All tools follow the consistent verb_noun pattern in snake_case (list_*, get_*, find_*). The naming is uniform and predictable, with no mixed conventions or vague verbs.

    Tool Count5/5

    Seven tools is well-scoped for a read-only ticketing information server. Each tool has a clear purpose and the count falls comfortably in the ideal 3-15 range.

    Completeness4/5

    The surface covers core retrieval workflows: events, performances, bookings, and customers. Minor gaps exist (e.g., no create/update operations, no direct booking-by-event search), but these align with a read-only information source and do not block typical usage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources