Terminal-based setup and login
Install the package once with npm, sign in with your existing Ticket Fairy account, and start by listing events from the terminal.
Ticket Fairy CLI
Ticket Fairy CLI is a command-line tool for promoters and event teams to manage Ticket Fairy events, exports, reporting, and other dashboard tasks from the terminal. It installs with npm and can also expose the same event data and actions to AI assistants through MCP.
Overview
Ticket Fairy CLI is a command-line interface for Ticket Fairy event operations. It lets promoters and event teams handle core dashboard tasks from the terminal, from event setup and brand selection to exports, reporting, and account work.
The product is designed for repeatable work: you can script changes, schedule jobs, and connect the CLI to other tools or AI assistants. It installs with npm, signs in as the Ticket Fairy user you already have, and supports macOS, Linux, and Windows with Node 20 or newer.
Features
Event lifecycle commands
Create, update, publish, postpone, cancel, reinstate, clone, and delete events, plus read event stats from the same command group.
Operational event tools
Create and manage ticket types, add-ons, tables, promo codes, invitations, messaging campaigns, and check-in status from the CLI.
Exports and reporting
Export orders and customers as CSV or JSON for spreadsheets, warehouses, or scheduled reports without copying data out of the dashboard.
Script-friendly automation controls
Use --from-file for repeatable create and update operations, stable JSON output, documented exit codes, idempotency keys, and dry-run support for safer automation.
AI assistant access via MCP
Start the built-in Model Context Protocol server so AI assistants can read and change events through the same account and permission model.
Use Cases
Repeatable event setup
Use the CLI to create, clone, or update events from files when you need to repeat the same setup across multiple shows or seasons.
Automated reporting
Schedule exports of orders and customers as CSV or JSON so reports can feed a spreadsheet, warehouse, or nightly job without manual copying.
Tool-to-tool workflows
Connect Ticket Fairy to Slack, a CRM, webhooks, or another script when you need event data to trigger work in outside systems.
AI-assisted operations
Let an AI assistant inspect live sales, check-in counts, and order data, then prepare changes or reports while staying within your permissions and approval guardrails.
Operational management from the terminal
Use team, invitation, promotion, messaging, and check-in commands for day-to-day event operations that would otherwise require switching between dashboard screens.
Pros and Cons
Pros
- Covers a broad set of ticketing workflows, including events, orders, customers, messaging, check-in, teams, tours, webhooks, and assets.
- Designed for automation, with JSON output, exit codes, idempotency keys, dry-run support, and --from-file payloads.
- Uses the same Ticket Fairy account and permissions you already have, so there is no separate integration account to manage.
- Includes a built-in MCP server for AI assistants such as Claude Code or other MCP clients.
- Supports standard operating environments on macOS, Linux, and Windows.
Cons
- Requires Node 20 or newer, so it is not usable on older Node environments.
- Vault banking commands are invitation only and only return data for brands enrolled in the Ticket Fairy Card programme.
- Some capabilities are only partially documented on the page, so readers may need the full command help for details.
FAQ
How do I set it up?
The CLI is installed with npm and requires Node 20 or newer. It opens a browser for sign-in, and on servers or in CI it can use a Personal Access Token via TICKET_FAIRY_API_KEY.
Who is this CLI for?
It is meant for promoters and event operators who want to script work that is otherwise done in the dashboard, such as event setup, exports, reporting, and AI-assisted workflows.
Can I use it in automation?
Yes. The CLI can output readable tables in a terminal and switch to JSON when piped, which makes it suitable for scripts, scheduled jobs, and pipelines.
What does it cost?
The page says the CLI is free with your Ticket Fairy account and MIT licensed. No separate account or API key request is required for normal use.
Can a team use it with existing permissions?
The CLI works with the Ticket Fairy account and brand you sign into, and the pages say every command runs with your existing permissions. The MCP mode can be started read-only or with changes allowed, depending on how you configure the client.
Quick Facts
- Category
- Developer Tool
- Platform
- macOS, Linux, Windows
- Runtime
- Node 20 or newer
- Distribution
- npm package
- License
- MIT
- Source domain
- ticketfairy.com
Альтернативы Ticket Fairy CLI
ByteAsk
ByteAsk is a terminal-first AI coding agent for C and C++ that edits repositories and verifies changes with the real compiler, debugger, sanitizers, and tests before showing a diff. It offers a free tier plus paid plans, with editor connectors and zero-retention handling described in the source.
Goldfish
Goldfish is an AI memory app for macOS that helps you reply, write, summarize, and continue using the context already on your Mac. It stores memory locally and writes in your tone.
CreateOS Sandbox
CreateOS Sandbox is an isolated compute environment for running code and agent workloads inside Firecracker micro-VMs. It is designed for workflows that need machine-level isolation, private networking between sandboxes, and programmatic control through SDK, CLI, or MCP.
ArtDeck
ArtDeck is a visual reference board app for iPhone, iPad, and Mac that lets artists collect mixed reference material on one canvas and study it with ToolBox lenses. It works offline, supports optional iCloud sync, and is sold as a one-time purchase with no account required.
Biji
Biji - это универсальная платформа, разработанная для повышения продуктивности с помощью инновационных инструментов и функций.
hob
hob is an independent workspace for coding agents that keeps agent sessions, terminals, history, and follow-up work organized around the tools and providers you already use. It is aimed at developers who want local control over routing, history, and workspace structure rather than a bundled model stack.