Connect to MCP-Compatible Tools – Ticket Generator

This article explains how to integrate Ticket Generator with LLM-powered tools such as ChatGPT, Claude Desktop, Cursor, LangChain, and other MCP-compatible clients using the Model Context Protocol (MCP).

Introduction

The Model Context Protocol (MCP) enables secure integration between a Ticket Generator account and AI-powered tools or development environments. Using MCP, AI agents can interact directly with Ticket Generator APIs to retrieve ticket and event data, generate ticket URLs, and send tickets programmatically.

This integration is ideal for developers and technical teams building AI-driven workflows for ticket management, event operations, and automated attendee communication.

A. Generate an API key from Ticket Generator

To securely connect Ticket Generator with an MCP-compatible tool, an API key is required.

Follow these steps to generate the API key:

Log in to the Ticket Generator dashboard
Create or select an event
Add a ticket design to the event
From the left sidebar, go to API
Click Get API Certification and then click Create
Enter the account password when prompted and click Verify
Copy the generated API key

This API key serves as the authorization credential for the MCP server. Store it securely and do not share it publicly.

For more details, refer to the step-by-step guide: Get API Key/Certificate

B. Configure the MCP client

Once the API key is generated, it must be added to the configuration file of the MCP-compatible tool.

Below are sample configurations for commonly used environments.

Cursor (`~/.cursor/mcp.json`)

{
  "mcpServers": {
    "ticket-generator": {
      "url": "https://your-server-url.com/mcp",
      "headers": {
        "Authorization": "YOUR_TICKET_GENERATOR_API_KEY"
      }
    }
  }
}

VS Code (`~/.vscode/mcp.json`)

{
  "mcpServers": {
    "ticket-generator": {
      "url": "https://your-server-url.com/mcp",
      "headers": {
        "Authorization": "YOUR_TICKET_GENERATOR_API_KEY"
      }
    }
  }
}

Claude Desktop

(~/Library/Application Support/Claude/claude_desktop_config.json)

{
  "mcpServers": {
    "ticket-generator": {
      "url": "https://your-server-url.com/mcp",
      "headers": {
        "Authorization": "YOUR_TICKET_GENERATOR_API_KEY"
      }
    }
  }
}

Replace YOUR_TICKET_GENERATOR_API_KEY with the API key generated in Section A.

C. Local development using ngrok

For local development, the Ticket Generator MCP server can be exposed using ngrok.

Follow these steps:

Install dependencies
```
npm install
```
Start the MCP server in HTTP mode
```
npm run dev:http
```
Expose the local server using ngrok
```
ngrok http 3000
```
Copy the ngrok forwarding URL (for example, https://abc123.ngrok-free.app)
Configure the MCP client using the ngrok URL

{
  "mcpServers": {
    "ticket-generator": {
      "url": "https://abc123.ngrok-free.app/mcp",
      "headers": {
        "Authorization": "YOUR_TICKET_GENERATOR_API_KEY"
      }
    }
  }
}

D. Supported tools and actions

The Ticket Generator MCP server supports multiple tools that can be triggered using plain-text prompts or directly via MCP-compatible applications.

Tool name	Description	Example phrase
get_ticket_data	Retrieve ticket data and information	“get ticket data”, “ticket info”
get_ticket_url	Generate a ticket URL for sharing	“get ticket link”, “ticket url”
send_ticket	Send tickets via email or other delivery methods	“send ticket”, “email ticket”
get_event_details	Retrieve event details and information	“get event details”, “event info”

These tools interact with the Ticket Generator APIs through the MCP layer to ensure secure and reliable execution.

E. MCP server endpoints

The Ticket Generator MCP server exposes the following endpoints:

GET /health — Health check endpoint
POST /mcp — MCP initialization and tool execution
GET /mcp — Server-to-client streaming notifications
DELETE /mcp — Session termination

The server runs in HTTP transport mode for both development and production environments.

F. Production deployment overview

For production deployment:

Deploy the MCP server to a hosting platform such as AWS or DigitalOcean
Set the required environment variables

export MCP_TRANSPORT=http
export PORT=3000
export HOST=0.0.0.0

Optional production variables include rate limiting, CORS configuration, JSON body size limits, and logging format.

After deployment, configure the MCP client with the production server URL:

{
  "mcpServers": {
    "ticket-generator": {
      "url": "https://your-production-domain.com/mcp",
      "headers": {
        "Authorization": "YOUR_TICKET_GENERATOR_API_KEY"
      }
    }
  }
}

G. Troubleshooting

Issue	Suggested action
“API key is required”	Ensure the API key is added under the Authorization header
“Invalid API key”	Regenerate the API key from the Ticket Generator dashboard
Connection error	Verify the server URL and internet connectivity
Tool not found	Restart the IDE and recheck the MCP configuration

The health of the MCP server can be verified by visiting the /health endpoint on the configured server URL.

If further assistance is needed

If you still have questions about MCP setup or Ticket Generator API access, you can explore more topics in this knowledge base or reach out to the customer relations team at support@ticket-generator.com