Issue and manage Apple Wallet & Google Wallet passes from any MCP-aware AI client.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent โ or use 1-click editor setup below.
๐ก Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Command-line interface for the PassNinja REST API.
Wraps /v1/pass_templates, /v1/passes, and /v1/webhooks so you can
manage Apple Wallet and Google Wallet passes from the shell.
From cmd.exe:
The script detects your CPU (amd64, arm64, or 386), downloads the matching
binary from the latest GitHub release, verifies its SHA256, drops it in
%LOCALAPPDATA%\Programs\passninja\, and adds that directory to your user
PATH. No admin needed; re-running upgrades in place.
Pin a specific version, or override the install directory:
If you already use Scoop:
.mcpb install)For chat-driven pass workflows, install the PassNinja MCP server into Claude Desktop:
Download passninja.mcpb
from the latest release.
Double-click the file. Claude Desktop opens an install dialog showing the 31 tools the server exposes (pass templates, issued passes, webhooks, scan-event applications and readers).
The dialog prompts for your API key and account ID โ get them at https://www.passninja.com/settings โ API key.
Hit Install, restart Claude Desktop, then ask Claude things like:
List my passninja pass templates and tell me how many passes are installed on each.
Issue a new pass on ptk_0x002 for jane@example.com.
The bundled binary is code-signed with Apple Developer ID and notarized, so
macOS Gatekeeper accepts it without prompts. Same .mcpb works on macOS
(universal), Linux (amd64), and Windows (amd64).
The server is also listed in the official MCP Registry
as io.github.flomio/passninja-cli, so any MCP client that consumes the
registry can discover and install it automatically.
Or pass credentials via env / flags:
Flag > env > ~/.passninja-auth.json > ~/.passninja.yaml > defaults.
The same precedence applies to the MCP server: passninja mcp (started by
Claude Desktop and other MCP clients) reads PASSNINJA_API_KEY /
PASSNINJA_ACCOUNT_ID from its environment, falling back to the auth file.
The CLI also doubles as a Model Context Protocol
server. The .mcpb install above wires this into Claude Desktop, but you can
hook it into any MCP client (Cursor, Cline, Zed, etc.) by configuring the
client to launch:
Tool surface (snake_case names mirror the CLI subcommands):
Each tool's input schema, destructive-hint annotations, and rich descriptions let the LLM self-discover correct usage without external documentation.
| Flag | Mode |
|---|---|
--json | Pretty-printed JSON |
--plaintext | Tab-separated, no decoration (good for piping to awk) |
| default | Bordered ASCII table |
Set a session-wide default via ~/.passninja.yaml:
The CloudEvents 1.0 type taxonomy emitted by passninja-site:
| Event type | When it fires |
|---|---|
pn.pass.installed | First device installs an issued pass |
pn.pass.updated | Pass fields change via PATCH/PUT |
pn.pass.uninstalled | Last device removes the pass |
pn.pass.scanned | A reader records a scan event (carries scanId, readerSerial, result) |
Reserved for future use: pn.pass.issued, pn.pass.deleted,
pn.pass_template.created, pn.pass_template.updated,
pn.pass_template.deleted.
Cloud-connected readers (VTAP Cloud, Famoco Tap&Go) post scans to PassNinja
themselves. A simple reader โ Reyax RYRR30D, ACS WalletMate, Elatec TWN4 โ
has no cloud connection of its own, so reader serve supplies one: it takes
the values the reader captures, submits them as scan events, and applies the
LED/beep instruction the server returns.
Setup is three steps, and only the last one runs on the reader host:
serve authenticates as that one reader with its bearer token โ a reader
host never needs, and should never hold, your account API key.
Tap values arrive on stdin (one per line) or over a loopback HTTP
endpoint with --listen 127.0.0.1:8080, which a driver POSTs to. A value
that looks like raw captured APDUs is forwarded for server-side decryption;
anything else is treated as an already-decrypted pass serial.
Each result is one JSON object on stdout:
To drive a physical LED, use the outcome hooks โ they receive $PN_RESULT,
$PN_LED, $PN_MESSAGE, $PN_PASS, and $PN_SCAN_ID:
Heartbeats (default every 5m) report liveness plus the hardware identity you
pass with --serial / --manufacturer / --model / --firmware, which is
what fills in the reader's Hardware panel in the dashboard. Readers whose
vendor MDM already tracks them should use --no-heartbeat.
No reviews yet โ be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/passninja)<a href="https://allmcps.com/mcp/passninja"><img src="https://allmcps.com/api/badge/passninja?style=directory" alt="PassNinja on AllMCPs" /></a>