Skip to main content
Glama
marek-knappe

TryBooking MCP Server

by marek-knappe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to TryBooking MCP Server

No user-submitted related servers found.

    Related Servers

    • tickiti-mcp by tickiti

      tickiti-mcpofficial

      tickiti
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that exposes the Tickiti helpdesk API to AI assistants, enabling ticket management and helpdesk operations via natural language.
      11
      MIT

    • threatlocker-mcp-server

      BigfootBytes
      A
      license
      A
      quality
      A
      maintenance
      MCP server for interacting with the ThreatLocker Portal API, enabling querying of computers, applications, policies, audit logs, and more through AI assistants.
      18
      1
      GPL 3.0

    • Shotgun MCP

      n4th4ndev
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes aggregated Shotgun event sales, net revenue, ticket quotas, and audience stats to AI assistants via natural language queries.
      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 15 tools

    Disambiguation5/5

    All tools have distinct purposes, covering different resources like transactions, bookings, events, sessions, sales, and scanning. Even though many start with 'get', their targets are clearly differentiated by resource type and context.

    Naming Consistency4/5

    14 out of 15 tools follow the 'get_{resource}' pattern. The only exception is 'list_events', which uses 'list' instead of 'get'. This minor inconsistency reduces the score.

    Tool Count4/5

    15 tools is reasonable for a read-only ticketing API. It covers many query aspects without being overwhelming or too sparse, though a few more could be added for completeness.

    Completeness2/5

    The tool set is entirely read-only, lacking any write operations such as creating, updating, or deleting bookings, events, or tickets. This is a significant gap for a ticketing system where transaction processing is expected.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources