WalletPassBuilder

com.walletpassbuilderPublished by walletpassbuilder.comOfficial publisherv1.0.0Updated Oct 24, 2026

Create, update and message Apple Wallet and Google Wallet passes and loyalty cards.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant create, update and message Apple Wallet and Google Wallet passes and loyalty cards through a hosted remote endpoint.

What you can do
WalletPassBuilder is a remote MCP server for working with digital wallet passes. According to its description, it lets an assistant create, update and message Apple Wallet and Google Wallet passes and loyalty cards. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when you want an assistant to help manage digital wallet passes or loyalty cards for Apple Wallet or Google Wallet, for example creating or updating passes as part of a customer program.
Requirements
A remote MCP connection to the provider's hosted endpoint over streamable HTTP. Authentication is required and uses OAuth, so the assistant must be authorized through the provider's OAuth flow. No environment variables or headers are declared.
Before you install
The server requires OAuth authorization, granting it access to the connected account. Its description mentions updating and messaging passes, which can change or send data to pass holders. No tool list is published, so review the permissions requested during authorization before connecting.

Installation

In SourceWeft

  1. Open WalletPassBuilder in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.walletpassbuilder%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "walletpassbuilder": {
      "type": "http",
      "url": "https://walletpassbuilder.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 11, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.