Ticket Generator

Provides ticket and event data access, URL generation, and sending tickets via MCP clients.
  • javascript

0

GitHub Stars

javascript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You use this MCP server to connect AI agents with the Ticket Generator APIs, enabling operations like retrieving ticket and event data, generating shareable ticket URLs, and sending tickets through delivery methods. It acts as a bridge that lets AI assistants access Ticket Generator functionality in a secure, HTTP-based flow.

How to use

Connect your MCP client to the ticket generator MCP server using HTTP transport. The server exposes tools that let your agents fetch ticket data, obtain shareable URLs, send tickets to recipients, and pull event details. Use the HTTP endpoints to initialize the MCP session, call the available tools, and stream server-to-client notifications as needed.

How to install

Prerequisites: Node.js 18.0.0 or higher. A Ticket Generator API key. For development, ngrok to expose your local server.

# 1. Install dependencies
npm install

# 2. Start the server in HTTP mode (development)
npm run dev:http

# 3. Expose your local server with ngrok
ngrok http 3000

Additional setup and configuration

Configure your MCP client to connect to the HTTP MCP server using the ngrok URL for local development or your production URL for deployment. Include the Authorization header with your Ticket Generator API key in every request.

{
  "mcpServers": {
    "ticket_generator_http": {
      "url": "https://your-ngrok-url.ngrok-free.app/mcp",
      "headers": {
        "Authorization": "your_ticket_generator_api_key"
      }
    }
  }
}

Security notes

The API key is sent in the Authorization header from your MCP client configuration. It is not stored in environment variables on the server and remains session-specific. All traffic flows over HTTPS in production or through the ngrok tunnel during development.

Production deployment steps

When ready for production, deploy the server to your hosting platform and configure environment variables to run in HTTP mode.

# Example production setup
export MCP_TRANSPORT=http
export PORT=3000
export HOST=0.0.0.0

# Optional production settings
export CORS_ORIGINS="https://yourapp.com"
export RATE_WINDOW_MS=60000
export RATE_MAX=60
export JSON_LIMIT=200kb
export LOG_FORMAT=combined

npm start

Server endpoints and tools

The server provides endpoints to check health and manage MCP sessions, plus a set of tools for interacting with Ticket Generator data and events.

Troubleshooting and tips

If you encounter authorization or network issues, verify that your API key is correctly provided in the Authorization header for every MCP client configuration, and confirm the ngrok URL or production URL is reachable from your client.

Examples of typical use cases

  • Retrieve detailed ticket data by ticket ID and related event or user IDs.

  • Generate a shareable URL for a specific ticket in web, mobile, or PDF format.

  • Send a ticket to a recipient via email with an optional custom message.

  • Fetch event details and optionally include ticket or attendee information.

Available tools

get_ticket_data

Retrieves ticket data and information from the Ticket Generator API using the provided ticket_id. Optional filters include event_id and user_id to scope the data.

get_ticket_url

Generates a shareable URL for a ticket. Supports format options such as web, mobile, or pdf and can include related event/user context.

send_ticket

Sends a ticket to a recipient via the chosen delivery method (email, sms, whatsapp) with an optional custom message.

get_event_details

Fetches event details from the Ticket Generator API and can include related ticket or attendee information if requested.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational