Walletap
Let your agent create and manage Apple Wallet and Google Wallet passes through Walletap while you build loyalty, tickets, or membership flows.
Overview
Walletap is a Build-phase MCP server that lets coding agents issue and manage Apple Wallet and Google Wallet passes via the Walletap API.
What is this MCP server?
- npm package @walletap/mcp-server v0.1.3 with stdio MCP transport
- Requires WALLETAP_API_KEY from app.walletap.io
- Issue and manage Apple Wallet and Google Wallet passes from the agent
- GitHub repository ivangr1/walletap-mcp
- Wallet platform MCP—not a mobile app template or store listing skill
- Server version 0.1.3 npm identifier @walletap/mcp-server
- One documented environment variable: WALLETAP_API_KEY
- stdio transport; registryType npm per server.json
What problem does it solve?
Wallet pass infrastructure is tedious to prototype, so indie teams delay loyalty and ticket features until late in the build.
Who is it for?
Indie developers shipping mobile-adjacent SaaS, events, or memberships who want wallet passes driven from the agent workspace.
Skip if: Products with no wallet use case or teams blocked from using third-party wallet SaaS for compliance reasons.
What do I get? / Deliverables
After adding the MCP server and API key, your agent can create and manage wallet passes through Walletap instead of manual dashboard clicks.
- Working MCP bridge to create and manage Walletap passes
- Agent workflows for wallet pass lifecycle during feature development
- Reduced manual work in the Walletap dashboard for iteration
Recommended MCP Servers
Journey fit
Wallet pass issuance is an external API integration you implement alongside your app—canonical placement is Build even when the passes support Grow retention later. Walletap MCP maps to wiring a third-party wallet platform into your product, not ideation or ops monitoring.
How it compares
Wallet pass API MCP integration, not a native iOS/Android codegen skill or App Store optimization pack.
Common Questions / FAQ
Who is Walletap MCP for?
Solo builders and small teams implementing Apple or Google Wallet passes who want agent-driven create-and-update flows via Walletap.
When should I use Walletap MCP?
Use it during Build when wallet passes are part of your MVP or beta—not before you have a concrete pass type and Walletap account.
How do I add Walletap to my agent?
Install @walletap/mcp-server from npm, set WALLETAP_API_KEY from app.walletap.io in the MCP server environment, and register the stdio server in Claude Code or Cursor.