About PassFast
PassFast is a hosted HTTPS MCP server for creating and managing Apple Wallet and Google Wallet passes. It is for MCP clients that need pass templates, issuance, updates, and sharing through a secret-key-authenticated API.
Key features
- 01List and publish pass templates
- 02Generate Apple and Google Wallet passes
- 03Download .pkpass files
- 04Update or void passes
- 05Create share links and QR codes
- 06Manage apps, organizations, and keys
Use cases
- 01Generate a dual-wallet pass from an MCP client
- 02Download a generated .pkpass file
- 03Update or void an issued pass
- 04Share a pass using a link or QR code
MCP support
Exposes PassFast pass-management capabilities to MCP clients over hosted HTTPS at https://passfa.st/mcp. Authentication uses a secret key; the repository contains install metadata and configuration examples, not a local server binary.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://passfa.st/mcpclaude mcp add --transport http st-passfa-passfast https://passfa.st/mcp{"mcpServers":{"st-passfa-passfast":{"type":"http","url":"https://passfa.st/mcp"}}}Open in Cursor{"servers":{"st-passfa-passfast":{"type":"http","url":"https://passfa.st/mcp"}}}Open in VS Code{"mcpServers":{"st-passfa-passfast":{"type":"http","url":"https://passfa.st/mcp"}}}{"mcpServers":{"st-passfa-passfast":{"serverUrl":"https://passfa.st/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://passfa.st/mcpAuth requiredTools
47| Parameter | Type | Required | Description |
|---|---|---|---|
| data | object | Yes | Dynamic field values merged into the template structure. |
| x_app_id | string | No | Override X-App-Id for this call. Omit the connection header by default; set it only for multi-app orgs. |
| locations | array | No | GPS locations where the pass is relevant (shown on lock screen). Overrides template defaults if provided. |
| expires_at | string | No | Optional expiration timestamp for the pass. |
| external_id | string | No | Optional external identifier for cross-system lookups. |
| template_id | string | Yes | ID of the published template to use. |
| wallet_type | enum | No | Target wallet platform. Defaults to `apple`. When set to `google`, the response is a JSON object with a `save_url` instead of a binary .pkpass file. When set to `both`, generates both Apple and Google passes in one call and returns a JSON object with `apple`, `google`, and `warnings` keys.apple | google | both |
| max_distance | number | No | Maximum distance in meters from a location for lock screen relevance. |
| get_or_create | boolean | No | When true, if a pass with the same serial_number already exists and is active, return the existing .pkpass (200) instead of a 409 error. The response includes an `X-Pass-Existed: true` header. If the existing pass is voided/expired, returns 409. When false (default), duplicate serials always return 409. |
| relevant_date | string | No | ISO 8601 date when the pass is relevant (appears on lock screen). |
| serial_number | string | Yes | Unique serial number for this pass. |
| strip_image_id | string | No | Override the template's strip/hero image for this pass only. The referenced image must belong to the same app and have purpose `strip` (or a `strip_*` variant). Applied to Apple `strip.png` and Google `heroImage` atomically (same value for both wallets in `wallet_type: "both"`). Omit or send `null` to use the template's strip image. |
Details
From the project READMEPassFast MCP
Remote HTTPS Model Context Protocol server for PassFast — Apple Wallet + Google Wallet passes from any MCP client (Cursor, Claude, ChatGPT, Codex, Grok).
| Endpoint | https://passfa.st/mcp |
| Alias | https://passfa.st/api/mcp |
| Docs | https://passfa.st/docs/mcp · https://passfa.st/mcp.md |
| OpenAPI | https://passfa.st/openapi.yaml |
| Signup / keys | https://passfa.st/signup |
| Privacy / Terms | https://passfa.st/privacy · https://passfa.st/terms |
This repository is the public metadata + install kit for marketplace listings (official MCP Registry, Grok Build plugins, open directories). The server itself is hosted at passfa.st — there is no local stdio binary here.
Auth
Authorization: Bearer sk_live_YOUR_SECRET_KEY
X-App-Id: YOUR_APP_ID # optional for single-app orgs
- Secret keys only (
sk_live_). Publishablepk_live_keys are rejected. - No OAuth, no PassFast agent account — the MCP client is the agent.
- Member/invite tools need a user JWT and are out of scope for key-auth MCP v1.
Install
Cursor
Copy cursor/mcp.json into ~/.cursor/mcp.json or project .cursor/mcp.json, then replace the placeholders.
Claude (HTTP)
{
"mcpServers": {
"passfast": {
"type": "http",
"url": "https://passfa.st/mcp",
"headers": {
"Authorization": "Bearer sk_live_YOUR_SECRET_KEY",
"X-App-Id": "YOUR_APP_ID"
}
}
}
}
Stdio-only clients: npx mcp-remote https://passfa.st/mcp with the same headers via your client’s env/header support.
Generic / registry
See server.json for the official MCP Registry remote descriptor (Streamable HTTP + auth headers).
What agents can do
- List / publish templates; generate dual-wallet passes; download
.pkpass - Update / void passes; share links + QR
- Upload images & signing credentials; manage apps / org / API keys
- Same billing as the HTTP API (see https://passfa.st/#pricing)
Starter prompts
Marketplace submissions
Prepared listing fields live under listings/. Status checklist: SUBMIT.md.
License
MIT © Aberkane Software
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.