passninja

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.

Install

macOS / Linux (Homebrew)

brew tap flomio/passninja
brew install passninja

Windows (PowerShell)

irm https://github.com/flomio/passninja-cli/releases/latest/download/install.ps1 | iex

From cmd.exe:

powershell -ExecutionPolicy Bypass -Command "irm https://github.com/flomio/passninja-cli/releases/latest/download/install.ps1 | iex"

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:

$env:PASSNINJA_VERSION = 'v1.2.3'
$env:PASSNINJA_INSTALL_DIR = 'C:\tools\passninja'
irm https://github.com/flomio/passninja-cli/releases/latest/download/install.ps1 | iex

Windows (Scoop)

If you already use Scoop:

scoop bucket add flomio https://github.com/flomio/scoop-passninja
scoop install passninja

Claude Desktop (one-click .mcpb install)

For chat-driven pass workflows, install the PassNinja MCP server into Claude Desktop:

1. Download passninja.mcpb

from the latest release.

1. Double-click the file. Claude Desktop opens an install dialog showing the

19 tools the server exposes (pass templates, issued passes, webhooks).

1. The dialog prompts for your API key and account ID —

get them at https://www.passninja.com/settings → API key.

1. 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 [email protected].

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.

Authenticate

passninja auth
# Pastes your API key and account ID; verifies by hitting /v1/pass_templates
# and saves credentials to ~/.passninja-auth.json (0600).

Or pass credentials via env / flags:

export PASSNINJA_API_KEY=...        PASSNINJA_ACCOUNT_ID=aid_0x002
passninja --api-key=... --account-id=... pass-template list

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.

Stdio MCP server

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:

passninja mcp

Tool surface (snake_case names mirror the CLI subcommands):

whoami
pass_template_{list, get, required_fields, reader_config, create, delete}
pass_{list, get, create, update, delete, raw, decrypt}
webhook_{list, get, create, delete, results}

Each tool's input schema, destructive-hint annotations, and rich descriptions let the LLM self-discover correct usage without external documentation.

Commands

passninja auth                                       Save API credentials
passninja whoami                                     Show the active credential / account
passninja version

passninja pass-template list
passninja pass-template get <ptk_0x...>
passninja pass-template required-fields <ptk_0x...>
passninja pass-template reader-config <ptk_0x...>          # NFC reader config (merchant id, collector, EC keys)
passninja pass-template create --name --platform --style    # enterprise only
passninja pass-template delete <ptk_0x...> [--yes]          # enterprise only

passninja pass create <ptk_0x...> [--field k=v | --data @file.json | --data '<json>']
passninja pass list <ptk_0x...>
passninja pass get <ptk_0x...> <pass_id>
passninja pass raw <ptk_0x...> <pass_id>
passninja pass update <ptk_0x...> <pass_id> [--field k=v | --data ... | --replace]
passninja pass delete <ptk_0x...> <pass_id> [--yes]
passninja pass decrypt <ptk_0x...> [--payload <b64> | --payload-file <path> | <stdin>]

# Enterprise only:
passninja webhook create --name --url --event <type> [--event <type> ...] [--pass-template ptk_0x...]
passninja webhook list [--page --per-page --pass-template]
passninja webhook get <webhook_id>
passninja webhook delete <webhook_id> [--yes]
passninja webhook results <webhook_id> [--page --per-page]

Output formats

Set a session-wide default via ~/.passninja.yaml:

default_output: json    # one of: table | json | plaintext
base_url: https://api.passninja.com/v1

Webhook events

The CloudEvents 1.0 type taxonomy emitted by passninja-site:

Reserved for future use: pn.pass.issued, pn.pass.deleted, pn.pass_template.created, pn.pass_template.updated, pn.pass_template.deleted.

passninja webhook create returns the bearer token once on creation. Save it — it will not be shown again.

Build from source

git clone https://github.com/flomio/passninja-cli.git
cd passninja-cli
make build                 # writes dist/passninja
./dist/passninja version
make install               # installs to $GOPATH/bin

Release flow

Tag-driven. Push a vX.Y.Z tag on master; the GitHub Actions workflow at .github/workflows/release.yml matrix-builds darwin/linux × arm64/amd64, packages a code-signed + Apple-notarized passninja.mcpb on a macOS runner, publishes both the binaries and the .mcpb on the GitHub Release, and opens a PR against flomio/homebrew-passninja bumping the formula url and sha256.

Apple credentials live in repo secrets (APPLE_TEAM_ID, APPLE_API_KEY_ID, APPLE_API_ISSUER_ID, APPLE_SIGN_IDENTITY, APPLE_CERTIFICATE_PASSWORD, plus the base64-encoded APPLE_API_KEY_P8 and APPLE_CERTIFICATE_P12).

After each tagged release, the MCP Registry entry needs a refresh. Bump packages[0].identifier, packages[0].version, packages[0].fileSha256, and the top-level version in server.json to match the new release, then:

mcp-publisher login github      # one-time per machine
mcp-publisher publish