accessoticketing-mcp
Read accesso Passport ticket orders from an emailed ticket link (no login; the link is the credential).
Get an order and every admission with compact/full views and optional terms.
Get one admission in full detail by index.
Save/download scannable barcode PNGs locally, inline, or via hosted expiring links.
Get Google Wallet save links for tickets.
Resolve email click-tracking links into direct accesso ticket URLs.
Check accesso reachability and whether a default ticket link is configured.
Most tools are read-only; barcode saving may write files or return download links.
Provides Google Wallet save links for tickets on an accesso Passport order, allowing them to be added to Google Wallet.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@accessoticketing-mcp Show me my order details from the ticket link."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
accessoticketing-mcp
An MCP server for accesso Passport mobile ticket links — the URL a venue emails you after a purchase. Reads the order and every admission on it, the scannable barcodes, and Google Wallet save links.
accesso powers ticketing for a lot of theme parks, water parks, camps, museums and festivals, so one server covers all of them: the merchant is encoded in the link.
Developed and maintained by AI (Claude Code). Use at your own discretion.
What it needs
No login. These links carry their own credential — the oToken in the query
string is what authorises the read. There is no account, no password, no browser
session, and no bot wall.
That also meansthe link is a secret. Anyone holding it can view and add the order's tickets. Treat it like a password: don't paste it into issues, logs or chats. This server redacts the tokens from its own output and error messages.
Related MCP server: tokenless-zendesk-mcp
Install
npx -y @chrischall/accessoticketing-mcp// claude_desktop_config.json / .mcp.json
{
"mcpServers": {
"accessoticketing": {
"command": "npx",
"args": ["-y", "@chrischall/accessoticketing-mcp"],
"env": { "ACCESSO_TICKET_URL": "https://media-engine.na3.accessoticketing.com/tickets/v1/..." }
}
}
}ACCESSO_TICKET_URL is optional — it just saves passing url on every call. The
server starts fine without it and reports the missing link on first use.
Variable | Required | Purpose |
| no | Default ticket link, used when a tool is called without |
| no | Where |
| no | Set to |
Tools
Tool | Does |
| The order and every admission: product, participant, date, start time, instructions. Returns the slim per-ticket list by default; |
| One admission in full, by |
| Locally, writes barcode PNGs and returns paths. Hosted, returns the images inline (with a download link for any past the size cap), or one expiring download link per barcode with |
| Google Wallet save links for the tickets. |
| Unwraps an email click-tracking link to the accesso URL it hides. |
| Confirms reachability and whether a default link is configured. |
Nothing here mutates an order. Every tool is read-only except accesso_save_barcodes, which writes PNG files to disk (never overwriting one) on a local install, or to the host's blob store behind a signed, expiring link when hosted, unless asked for inline images.
> what do we have booked tomorrow?
9:00 AM Tiny Trekkers Full-Day (Ages 4-7) — one participant
9:00 AM Whitewater Kayak Camp I: Intro — two participants
all-day Lunch / Snack / Early Drop-Off — nine more admissionsUpgrading
next release
accesso_save_barcodes no longer writes to the server's disk on a hosted
deployment (mcp-host). Local installs are unchanged: same files, same
{ outputDir, saved: [{ index, participant, packageName, path }] } result.
Hosted,
inline: false(or a server with a writable disk AND a blob store, called withoutinline): returns{ order, note, saved: [{ index, participant, packageName, barcodeText, url, expiresAt }] }— one signed download link per barcode, expiring atexpiresAt. There is nooutputDirand nopath. Previously a hosted server withoutACCESSO_NO_FILE_OUTPUTwrote the PNGs to the runner's disk and returned paths nobody could open.Inline results (
returned,tickets, …) gainlinked: [{ …, url, expiresAt }]andlinkNotewhen a blob store is available: barcodes past the inline size cap now come back as links instead of being dropped, soomittedForSize/omittedIndexesonly appear when there is no blob store. With no blob store andinline: false(nowhere to save), the inline result carries anotesaying so.When not a single barcode fits the inline cap and there is no link or disk route, the tool now fails with a
too_largeerror instead of returning an empty image list.On a hosted deployment
ACCESSO_NO_FILE_OUTPUTis no longer needed, andaccesso_healthcheckreportsfilesPersist: falsethere.
Shell-out skill
Prefer a shell? skills/accesso-tickets/ does the same reading with curl and a
dependency-free parser, no server required. It ships with the package.
Notes on the data
date/timeare the merchant's local wall-clock strings with no timezone attached. They are passed through verbatim rather than converted.Merchant-specific detail rows (
Guest Number,Web Sales ID, …) are harvested generically intodetails, so a venue this was never tested against still works.An expired link returns HTTP 200, not an error status — the server detects the body and says the link is expired rather than reporting zero tickets.
Development
npm install
npm run build
npm test
npm run test:coverage # 100% thresholds, enforced in CISee docs/ACCESSO-API.md for the captured request/response shapes and CLAUDE.md
for repo conventions.
License
MIT
Available Tools
6 toolsaccesso_get_orderARead-only
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.
Inputs: url, view, include_terms.
accesso_get_ticketARead-only
One admission from an accesso order in full detail, including the merchant instructions and (on request) the terms. Identify it by its index from accesso_get_order.
Inputs: index (required), url, include_terms.
accesso_get_wallet_passesARead-only
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.
Inputs: url, indexes.
accesso_healthcheckARead-only
Check that this server can reach accesso and whether a default ticket link is configured.
Inputs: url.
accesso_resolve_linkARead-only
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.
Inputs: url (required).
accesso_save_barcodesA
Save the scannable barcode images from an accesso order. Run locally, writes PNGs and returns their paths. Run remotely (hosted), returns the images inline by default, with a download link for any past the size cap; set inline to false for one expiring download link per barcode instead. Set inline to true to receive the images directly in any deployment.
Inputs: url, inline, indexes.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
The tools mostly target distinct actions: order summary, single-ticket detail, barcode saving, wallet passes, link resolution, and health checking. `accesso_get_order` and `accesso_get_ticket` have some conceptual overlap, but the latter is clearly scoped to one admission identified by index.
Almost all tools use the `accesso_verb_noun` pattern (`get_order`, `get_ticket`, `save_barcodes`, `resolve_link`). `accesso_healthcheck` is a minor deviation because it is a noun rather than a verb_noun name.
Six tools is well-scoped for a focused ticket-link access server. Each tool covers a distinct operation without obvious redundancy.
The surface covers the core read-only workflow: resolving links, reading order and ticket details, saving barcode images, obtaining wallet passes, and checking connectivity. No obvious lifecycle gaps exist for this domain.
Maintenance
Related MCP Connectors
Screenshots, PDFs, image editing, QR codes, email validation and more through one hosted MCP server.
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
2,000+ MCP servers read at source level. Know what one does before you connect. Free, no key.
A paid remote MCP for hosted MCP server, built to return verdicts, receipts, usage logs, and audit-r
Related MCP Servers
- AlicenseAqualityBmaintenanceAn MCP server that provides read-only access to MySQL databases.4896 npm75MIT
- AlicenseAqualityCmaintenanceMCP server that authenticates via browser session cookies to access Zendesk's REST API without API tokens, supporting reads and writes with agent permissions.1933 npm1MIT
- AlicenseAqualityDmaintenanceRead-only MCP server for the HIT ticket management system that lists queues, searches/fetches ticket details, and lists ticket templates.49 npm1MIT
- AlicenseAqualityDmaintenanceRead-only MCP server for Edenred Plus that enables checking benefit balances, transactions, and deals via local browser authentication.5MIT