AI assistants

Walletap runs a Model Context Protocol (MCP) server, so an AI assistant can work in your account directly. Ask for a loyalty card and the assistant uploads the artwork, designs the template and issues the first passes; ask it to add a stamp and the pass in the customer's wallet updates.

Before you start#

• A Walletap account. Sign-up is part of the connection flow, so you can create one there if you do not have one yet.
• An assistant that can connect to remote MCP servers: Claude, Claude Code, Cursor, ChatGPT, or any other MCP client.

How connecting works#

The server is at https://mcp.walletap.com. You add that address to your assistant once, sign in to Walletap, and approve what the assistant may do. There is nothing to install and no key to paste.

The assistant works in the Walletap account you sign in with. Sign in with the account that owns your templates.

Connect your assistant#

claude mcp add --transport http walletap https://mcp.walletap.com

Sign in and authorize#

The first time the assistant connects, a Walletap page opens.

1. Sign in

   Click Continue with Google, or enter your Email address and Password and click Sign in. New to Walletap? Click Create one to make an account here.

2. Review the access

   The Authorize access page lists what the assistant is asking to do, under This will allow the application to:.

3. Approve

   Click Authorize. You return to your assistant, which can now use Walletap.

Try it with "List my Walletap templates."

What the assistant may do#

What you approve on the Authorize access page decides which tools the assistant can use. Most assistants ask for the first three permissions together.

Sending messages is its own permission because it reaches your customers directly. Issuing an access badge gives a person a way through a door, so it is kept apart from issuing passes.

Tools#

Tools that only read are marked read-only to the assistant, so asking a question never changes anything. Tools that change something are marked as such, and most assistants ask you to confirm before using them.

Templates#

Passes#

create_pass delivers the pass. When a pass has an email address or phone number, Walletap sends the pass link to it, following your account's delivery settings, unless the assistant turns delivery off for that call.

Notifications#

Files, locations and team#

Access badges#

For accounts with access badges.

A badge must be published in the dashboard before anyone can be issued it.

Things to ask#

• "Create a loyalty card for Harbour Coffee: ten stamps for a free coffee, a dark green background, and our logo from https://harbour.example/logo.png."
• "Issue a Coffee Card to maya.chen@example.com with two stamps already collected."
• "Add a stamp to the Coffee Card for luka.horvat@example.com."
• "Tell everyone holding a Summer Jazz Night ticket that doors open at 19:00."
• "Export every Northside Membership pass as a CSV."
• "Translate the labels on the Spring Offer into German."
• "Who holds the Staff door badge?"

Example: a stamp card in one request#

Alex Morgan asks:

The assistant:

1. Calls upload_file_from_url with the logo address and gets back a file ID.
2. Calls create_template for a loyalty card with stamp collection on, ten stamps, and the uploaded logo. The reply links to the new template's design page in the dashboard.
3. Calls create_pass with Maya's email address and two collected stamps.
4. Reports the template, the pass and its add-to-wallet link.

Because the pass has Maya's email address, Walletap emails her the link.

Connect with an API key#

For a client that can send headers but cannot sign in with OAuth, use a Walletap API key from SettingsAPI keys. The assistant can then do what the key can do. See authentication for keys and their presets.

Remote. Send the key in an X-API-Key header to https://mcp.walletap.com. The client must accept both JSON and event streams:

curl -X POST https://mcp.walletap.com \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-API-Key: $WALLETAP_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_templates","arguments":{}}}'

Local. Run the server on your own machine with the open-source @walletap/mcp-server package. Any client that accepts a stdio command can use this configuration:

{
  "mcpServers": {
    "walletap": {
      "command": "npx",
      "args": ["-y", "@walletap/mcp-server"],
      "env": { "WALLETAP_API_KEY": "wtap_sk_..." }
    }
  }
}

The hosted server at https://mcp.walletap.com also carries the access badge tools.

Limits#

The server accepts 60 requests a minute for each account, or for each API key. Past that it answers Too many requests. Retry after a number of seconds, and the assistant should wait that long. For a large import, use the dashboard or the API directly.

Disconnect#

Remove Walletap from your assistant's connector or MCP settings. To connect again, add it and sign in as before.

If something goes wrong#

The assistant says it cannot connect. Remove the connector and add it again with exactly https://mcp.walletap.com — no trailing slash. Then sign in again.

"Invalid email or password" on the sign-in page. If you sign in to the dashboard with Google, use Continue with Google. To use an email address instead, set a password first: in the dashboard, go to SettingsAccount and click Reset password.

The Google window closes and nothing happens. The window was closed before sign-in finished. Close any leftover windows and click Continue with Google again.

A tool answers that it "requires scope" something. The connection was approved for fewer permissions than that tool needs. Remove the connector, add it again, and approve the permissions the assistant asks for.

A pass was issued, but the customer got no email or text. The email address or phone number has to be on the pass itself, and delivery must be on. The assistant can turn it on or off for each call; when it does not, your delivery settings decide.

"origin_not_allowed". A browser-based client on another website called the server. Use a desktop app, call the server from your own backend, or run the local package.

An access badge is refused as not_published. Publish the badge in the dashboard, then ask again. See access badges.

Next steps#