Log inSubmit server
Accessoticketing MCP logo

Accessoticketing MCP

Read accesso Passport ticket links to retrieve admissions, barcodes, and Google Wallet save links.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Accessoticketing MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "accessoticketing-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/accessoticketing-mcp"
      ],
      "env": {
        "ACCESSO_TICKET_URL": "YOUR_VALUE_HERE",
        "ACCESSO_OUTPUT_DIR": "YOUR_VALUE_HERE",
        "ACCESSO_NO_FILE_OUTPUT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

accessoticketing-mcp MCP server reads accesso Passport mobile ticket links and exposes order, admission, barcode, and Google Wallet data through MCP tools. It uses the credential embedded in each ticket URL, so no account login or browser session is required. Use it to inspect bookings, retrieve individual ticket details, save barcode images, or generate wallet links. The server is read-only apart from writing barcode PNG files when file output is enabled.

Use cases

  • Inspect accesso orders and admission details
  • Retrieve individual ticket information
  • Save ticket barcodes as PNG files
  • Generate Google Wallet save links
  • Resolve tracked ticket URLs from email

Key features

  • Reads accesso Passport mobile ticket links
  • Lists orders and admissions
  • Returns full ticket details by index
  • Saves or inlines barcode images
  • Generates Google Wallet links
  • Checks link reachability and configuration

Tools6

What Accessoticketing MCP lets your agent do. Expand a tool for its parameters.

Self-reported~140 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

5/5 checks healthy over the last 24d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @chrischall/accessoticketing-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.8kPackage downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Tools exposed6Callable tools this server registers over MCP.

How Accessoticketing MCP works

What accessoticketing-mcp MCP server does

The accessoticketing-mcp MCP server reads accesso Passport mobile ticket links issued after a purchase. A link can contain an entire order, including products, participants, dates, start times, instructions, admissions, and scannable barcodes. The merchant is represented by the link, so the same server can handle accesso-backed venues such as parks, camps, museums, and festivals when their ticket links use the supported format.

The server does not require an accesso account, password, browser session, or separate login. The URL carries an oToken query parameter that authorizes access. Because possession of the URL grants access to the order, the link should be handled like a password. The server removes tokens from its own output and error messages, but callers should also avoid exposing the original URL in logs, issues, or chat transcripts.

How it works

Provide a ticket URL to a tool, or configure ACCESSO_TICKET_URL as the default so calls can omit the URL. accesso_get_order returns a compact list of admissions by default and can return all parsed fields with view: "full". accesso_get_ticket retrieves one admission in full using its index.

The server preserves the merchant's date and time strings as local wall-clock values. It does not attach or calculate a timezone. Venue-specific rows, such as guest numbers or sales identifiers, are collected generically in a details structure rather than requiring a fixed list of merchant fields.

Expired links need special handling: accesso may respond with HTTP 200 even when a link is no longer valid. The server checks the response content and reports expiration instead of treating the result as an order with no tickets.

Setup and configuration

Run the package with npx -y @chrischall/accessoticketing-mcp and register it as an MCP server in the client configuration. Claude Desktop can launch it with the npx command and the package name. ACCESSO_TICKET_URL is optional; without it, the server starts and reports that a link is missing when a tool needs one.

ACCESSO_OUTPUT_DIR selects the directory used for barcode PNG files. By default, files go to the current working directory, with ~/Downloads used when the current directory is /, as can occur with Claude Desktop. Set ACCESSO_NO_FILE_OUTPUT=1 in environments where the server should not write to the local filesystem; barcode results are then returned inline.

Tools and capabilities

The accessoticketing-mcp MCP server exposes these operations:

  • accesso_get_order reads order and admission information, with compact and full views.
  • accesso_get_ticket returns one admission's complete parsed data by index.
  • accesso_save_barcodes writes barcode PNGs and returns their paths, or returns image data inline. Files are not overwritten.
  • accesso_get_wallet_passes returns Google Wallet save links.
  • accesso_resolve_link follows an email click-tracking URL to reveal the accesso ticket URL it contains.
  • accesso_healthcheck checks reachability and whether a default link is configured.

A shell-based skill included with the package provides similar reading through curl and a dependency-free parser, without running the MCP server.

Limitations and notes

The accessoticketing-mcp MCP server does not mutate ticket orders. Barcode saving is the only operation that writes data, and that write is limited to PNG output unless inline results are requested. Ticket URLs are bearer credentials, so anyone who obtains one may be able to view and add the order's tickets. Dates and times have no timezone metadata, and should not be interpreted as converted timestamps.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Accessoticketing MCP

accessoticketing-mcp is an MCP server that connects to accesso Passport mobile ticket links and reads their orders and admissions. Its main tools retrieve order or ticket details, save or inline barcodes, return Google Wallet save links, resolve tracked URLs, and check link reachability without requiring an accesso login.

Install it by configuring an MCP client to run `npx -y @chrischall/accessoticketing-mcp`. You can optionally set `ACCESSO_TICKET_URL` in the client environment to provide a default ticket link, or pass a URL to each tool call.

Set `ACCESSO_TICKET_URL` to the accesso Passport ticket link in the MCP server environment. This variable is optional; if it is absent, the server still starts and reports that a URL is missing when a tool requires one.

Yes, `accesso_save_barcodes` can write barcode PNG files and return their paths. Set `ACCESSO_OUTPUT_DIR` to choose the destination, or set `ACCESSO_NO_FILE_OUTPUT=1` so the tool returns images inline instead of writing to the filesystem.

Treat accesso ticket links as passwords because their embedded `oToken` authorizes access to the order. Do not put them in logs, issues, or chats. The server redacts tokens from its own output and error messages, but the original link remains sensitive.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAccessoticketing MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/accessoticketing-mcp?style=directory)](https://allmcps.com/mcp/accessoticketing-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/accessoticketing-mcp"><img src="https://allmcps.com/api/badge/accessoticketing-mcp?style=directory" alt="Accessoticketing MCP on AllMCPs" /></a>