accessoticketing-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACCESSO_OUTPUT_DIR | No | Where accesso_save_barcodes writes PNGs. Defaults to cwd. | |
| ACCESSO_TICKET_URL | No | Default ticket link, used when a tool is called without url. Optional — just saves passing url on every call. The server starts fine without it and reports the missing link on first use. | |
| ACCESSO_NO_FILE_OUTPUT | No | Set to '1' where the filesystem isn't the user's (a hosted deployment) so barcodes return inline. | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| accesso_get_orderA | Read an accesso ticket link: the order number and every admission on it — product, participant, date, start time, barcode text, and the merchant instructions. Covers any accesso-powered venue (theme parks, camps, festivals). Needs no login; the emailed link is the credential. |
| accesso_get_ticketA | One admission from an accesso order in full detail, including the merchant instructions and (on request) the terms. Identify it by its |
| accesso_save_barcodesA | Save the scannable barcode images from an accesso order. Writes PNGs and returns their paths; set inline to receive the images directly instead (which is the only useful mode when this server runs remotely, since its filesystem is not the user's). |
| accesso_get_wallet_passesA | Google Wallet save links for the tickets on an accesso order. Open one on a phone to add that ticket to Google Wallet. Not every merchant enables passes. |
| accesso_resolve_linkA | Turn an order-confirmation email's click-tracking link into the direct accesso ticket URL it wraps. Use when a link is not already an accessoticketing.com address. |
| accesso_healthcheckA | Check that this server can reach accesso and whether a default ticket link is configured. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a unique function: order retrieval, single ticket lookup, barcode saving, wallet passes, link resolution, and healthcheck. No overlapping purposes, so an agent can cleanly select the right tool.
All tools share the accesso_ prefix and follow a clear verb_noun pattern (get_order, get_ticket, save_barcodes, get_wallet_passes, resolve_link). The one exception, healthcheck, is a standard compound noun and does not break the overall consistency.
Six tools is well-scoped for a specialized ticketing integration. Each tool covers a distinct need without redundancy or bloat, and the count fits the narrow domain perfectly.
For a read-only accesso ticket-linking server, the surface is complete: fetch order, fetch ticket, save barcodes, generate wallet passes, resolve tracking URLs, and verify connectivity. No obvious dead ends or missing workflows.